Mario

For now we can't really get around having it extra like we did with monsters because of the loading order (might throw errors and such if we load items from...

> imo not worth fixing something that isn't broken > Mounts will soon break, because we exceed the limit we are reserving for it. > > current system has advantages...

Did you already benchmark? I would really like to see the results, because code wise this looks good to me but seeing some benchmark statistics wouldn't be bad at all.

You can also use `std::chrono::high_resolution_clock` that gives good results aswell.

sounds good to me, once you consider it "stable" and it looks good we should merge it, we can still do more optimizations over the time but this is a...

actually this entire thing should be handled completly in lua by coroutines and a simple addEvent timer at startup, could get rid of all c code then and we wouldn't...

I can do that on monday, I'm busy with work the entire weekend

This is a prime example of why using /reload is just a bad idea in general but I'm still curious how the script looks like , so post it please.

I can only agree with what @wo11ven here just said it would cause more confusion. Well, we have to agree that the way `onStepOut` is right now is not correct...

I don't mind about `fromPos` and `toPos` those where my first intentions anyway but as it would have caused a complete re work on all scripts with `onStepIn/onStepOut` I have...