Hello lunatics,
You may have wondered why I have implemented the realtime views for time attack and speed weekend, although that info is already available, e.g. ingame or through panzerborns site.
Well, I can tell you now: it was a preparation for the manual update feature.
It is used to enable you to force updates on my site as soon as your precious new times appear on the evo servers instead of waiting for them to appear on my site automatically! It can also be used to circumvent my top 1000 limit for time attack times.
As you might know, I update all speed weekend times and the best 1000 times of each time attack track/vehicle combo once per day, which results in a delay of 0,5 to 1,5 days between you doing it and others seeing it.
Now, if you want newer times or time attack times out of the top 1000 to appear on my site, all you have to do is display the time in the realtime view and then press the new "Update" button. Easy as that! Just keep in mind, that time attack times out of the top 1000 that you introduce this way are not automatically updated once you improve while the improved times are still out of the top 1000 range. You would have to repeat the manual update to load the improved time.
To keep the manual update simple, I always refresh the whole currently displayed realtime view. No need to select single racers.
The only requirement is, that the racers are already known in my database. That means they must have at least one speed weekend result or one time attack result within the top 1000 or they will be ignored by the update.
As a result of pressing "Update" you will see the reloaded page, followed by update status messages like these:
50 records above considered for update.
49 records are from known racers.
45 records of those are already in the database.
4 new records added to the database.
Update processing finished.
You may also see a message that the update is currently not possible. This is normal during the automatic update (usually for less than 5 minutes). If this situation persists over more than an hour, please drop me a note.
Now you know all the gory details.
Looking forward to someone using it - apart from me for my beachcomber rig :)
You may have wondered why I have implemented the realtime views for time attack and speed weekend, although that info is already available, e.g. ingame or through panzerborns site.
Well, I can tell you now: it was a preparation for the manual update feature.
It is used to enable you to force updates on my site as soon as your precious new times appear on the evo servers instead of waiting for them to appear on my site automatically! It can also be used to circumvent my top 1000 limit for time attack times.
As you might know, I update all speed weekend times and the best 1000 times of each time attack track/vehicle combo once per day, which results in a delay of 0,5 to 1,5 days between you doing it and others seeing it.
Now, if you want newer times or time attack times out of the top 1000 to appear on my site, all you have to do is display the time in the realtime view and then press the new "Update" button. Easy as that! Just keep in mind, that time attack times out of the top 1000 that you introduce this way are not automatically updated once you improve while the improved times are still out of the top 1000 range. You would have to repeat the manual update to load the improved time.
To keep the manual update simple, I always refresh the whole currently displayed realtime view. No need to select single racers.
The only requirement is, that the racers are already known in my database. That means they must have at least one speed weekend result or one time attack result within the top 1000 or they will be ignored by the update.
As a result of pressing "Update" you will see the reloaded page, followed by update status messages like these:
50 records above considered for update.
49 records are from known racers.
45 records of those are already in the database.
4 new records added to the database.
Update processing finished.
You may also see a message that the update is currently not possible. This is normal during the automatic update (usually for less than 5 minutes). If this situation persists over more than an hour, please drop me a note.
Now you know all the gory details.
Looking forward to someone using it - apart from me for my beachcomber rig :)