This one: https://www.php.net/manual/en/function.date.php, and this reference for the format string
edit: my data looks correct from here
edit: my data looks correct from here
PiranMOTODestructionDerby Season 15 Round 1
Stats at https://piranmoto.uk/events/240
Last edited by Racon, .
Minor updates for 2025
There is a 'custom access' setting, ie, the mod only shows for people whose usernames have been added to a list by the mod creator.
(Some people apparently get all the way into adulthood without ever having to learn about sharing, bless 'em)
(Some people apparently get all the way into adulthood without ever having to learn about sharing, bless 'em)
PiranMOTODestructionDerby Choose-Your-Own-Combos #9
Stats at https://piranmoto.uk/events/239
Last edited by Racon, .
Stats at https://piranmoto.uk/events/238
Last edited by Racon, .
I knew Kyoto had been expanded, but I had no idea by how much! It all looks stunning, too. Top job guys 
stats at https://piranmoto.uk/events/237
Last edited by Racon, .
61/racon/Jamie Tresidder/UK/PiranMOTO/Schancke T16
Copied from Discord:
Jon606 — Today at 00:30
@everyone
After a thorough review of the event held on 29th November (Season 14, Event 13) the following administrative actions have been taken:
PERMANENT BANS FROM PIRANMOTO
KESY White (starlet_man): multiple instances of hitting on blue flag in multiple events
KESY D (Rallidafu): multiple instances of hitting on blue flag to help a team mate
KESY Atte (Tahvis): toxic attitude throughout various events which has been carried over into the servers' Discord channel
ER'ChrisFI'DA (kristelis): toxic attitude throughout the event in question
Tadulis (PauliusE90i): continued rulebreaking despite having been unbanned previously
Vilius (Valdas1): continued rulebreaking despite having been unbanned previously
FINAL WARNINGS
the following drivers will be permanently banned if they break another rule
All these drivers are on final warnings due to teamracing:
KESY Halil (Elias_H)
KESY Jere (jeeret)
KESY Jonzu95 (Jonzu95)
KESY Nuutti (lanittaja234)
KESY Onni (superonni2277)
KESY Salminen (1996Tomppa)
The incidents which took place on 29th November were a disgrace to the entire concept of PiranMoto Open Destruction Derby. The biggest issue was of course the KESY "super team" which was the cause of multiple instances of poor behaviour that culminated in a complete loss of control by the end of the event. Destruction Derby racing is strictly one on one: while racing with team tags is allowed, racing with team tactics/strategy is forbidden. Having reviewed the races from the 29th November, it is clear the KESY team engaged in team tactics designed to bruteforce an event win. The admins are still none the wiser as to why this occurred as the drivers involved had raced previous weeks solo.
I would also like to refer drivers to the official PiranMoto Destruction Derby doctrine on the LFS Forum: https://www.lfs.net/forum/thread/106895-What-is-DD%3F-The-Destruction-Derby-Doctrine as the review included requests of incidents which followed the rules.
Jon606 — Today at 00:30
@everyone
After a thorough review of the event held on 29th November (Season 14, Event 13) the following administrative actions have been taken:
PERMANENT BANS FROM PIRANMOTO
KESY White (starlet_man): multiple instances of hitting on blue flag in multiple events
KESY D (Rallidafu): multiple instances of hitting on blue flag to help a team mate
KESY Atte (Tahvis): toxic attitude throughout various events which has been carried over into the servers' Discord channel
ER'ChrisFI'DA (kristelis): toxic attitude throughout the event in question
Tadulis (PauliusE90i): continued rulebreaking despite having been unbanned previously
Vilius (Valdas1): continued rulebreaking despite having been unbanned previously
FINAL WARNINGS
the following drivers will be permanently banned if they break another rule
All these drivers are on final warnings due to teamracing:
KESY Halil (Elias_H)
KESY Jere (jeeret)
KESY Jonzu95 (Jonzu95)
KESY Nuutti (lanittaja234)
KESY Onni (superonni2277)
KESY Salminen (1996Tomppa)
The incidents which took place on 29th November were a disgrace to the entire concept of PiranMoto Open Destruction Derby. The biggest issue was of course the KESY "super team" which was the cause of multiple instances of poor behaviour that culminated in a complete loss of control by the end of the event. Destruction Derby racing is strictly one on one: while racing with team tags is allowed, racing with team tactics/strategy is forbidden. Having reviewed the races from the 29th November, it is clear the KESY team engaged in team tactics designed to bruteforce an event win. The admins are still none the wiser as to why this occurred as the drivers involved had raced previous weeks solo.
I would also like to refer drivers to the official PiranMoto Destruction Derby doctrine on the LFS Forum: https://www.lfs.net/forum/thread/106895-What-is-DD%3F-The-Destruction-Derby-Doctrine as the review included requests of incidents which followed the rules.
I'd love to see that too. I've got an API-driven list here, but it's half-assed unfinished (adds new mods daily, but doesn't check/update any that are changed/deleted)
Stats at https://piranmoto.uk/events/236
Last edited by Racon, .
Stats at https://piranmoto.uk/events/235
Last edited by Racon, .
PiranMOTDestructionDerby s14e12
Stats at https://piranmoto.uk/events/234
Last edited by Racon, .
Stats at https://piranmoto.uk/events/233
Last edited by Racon, .
I'm just talking generally about insim programs rather than lapper-specific.
Mine can be setup with a separate insim if I follow a couple of rules when building the layout, that one just populates the database for the main insim to use.
It looks like you could automate the layout setup you've got though: read all the checkpoints in as the track loads and determine which ones are for clips from the coords/widths/headings automatically?
If you can get at, there's enough data about the car and checkpoint in the packet to work out a pretty good check with trigonometry just as it is, and with a little setup per mod I reckon you could make it really good.
(If only I didn't have a million other things to code, that's my kinda challenge
)
Mine can be setup with a separate insim if I follow a couple of rules when building the layout, that one just populates the database for the main insim to use.
It looks like you could automate the layout setup you've got though: read all the checkpoints in as the track loads and determine which ones are for clips from the coords/widths/headings automatically?
If you can get at, there's enough data about the car and checkpoint in the packet to work out a pretty good check with trigonometry just as it is, and with a little setup per mod I reckon you could make it really good.
(If only I didn't have a million other things to code, that's my kinda challenge
)If I'm remembering correctly, in order to reduce the freeze that happened when a new mod left the pits, some of the texture loading was deferred from then until later. I don't know how the client decides when is a good time, but it sounds like it takes a while for you sometimes.
I've seen it once when there was a lot of different mods on track at once, but it only lasts a minute or so for me. (Scared the life out of me for that minute because it was one of my mods that I had just updated... I thought I had messed up the upload)
I've seen it once when there was a lot of different mods on track at once, but it only lasts a minute or so for me. (Scared the life out of me for that minute because it was one of my mods that I had just updated... I thought I had messed up the upload
)FGED GREDG RDFGDR GSFDG