Normal
I'm guessing he does it the same way Sledmore implemented it into his Plus Emulator (ProcessComponent) which was inspired by Matty from his Mango server. RP emulator's rarely have anything going on under the hood of it's timers besides maybe a simple alert, coin update, etc. it would be considered a waste of resources imo to create Tasks also because the user could stop and restart their timer at any minute just by a simple interaction and the emulator would then have to stop and schedule a new Task. Using 1 timer per session that's literally a pooled Thread and just using creating a ticker in the "core loop" (since it's necessary yet rarely has anything going on under the hood anyways) seems much more efficient.No way could I possibly see someone replacing the core loop (pooled Thread with a loop) for Task(s), but I can see you replacing the ticker with a Task for more strenuous timers not ones that just play with integers and booleans.
I'm guessing he does it the same way Sledmore implemented it into his Plus Emulator (ProcessComponent) which was inspired by Matty from his Mango server. RP emulator's rarely have anything going on under the hood of it's timers besides maybe a simple alert, coin update, etc. it would be considered a waste of resources imo to create Tasks also because the user could stop and restart their timer at any minute just by a simple interaction and the emulator would then have to stop and schedule a new Task. Using 1 timer per session that's literally a pooled Thread and just using creating a ticker in the "core loop" (since it's necessary yet rarely has anything going on under the hood anyways) seems much more efficient.
No way could I possibly see someone replacing the core loop (pooled Thread with a loop) for Task(s), but I can see you replacing the ticker with a Task for more strenuous timers not ones that just play with integers and booleans.