setlevel2 / onPlayerEnters issue
 

If you use setlevel2 to change a players level, and the player is already located in that level, all timeouts in attached ganis (obj.attr[#] = "gani" etc.) completely halt, and you're unable to reinitialize them since onPlayerEnters() will not be triggered by the warp (clientside nor serverside).

I worked around it by only changing x/y if the player is already in the destination level, but I find it to be a short term solution to a long term issue. Is there anything else I can use to reinitialize the timeout in the gani script?

Call onPlayerEnters() manually?

And just how do you propose I call the onPlayerEnters() function inside the attached gani from an external script? onPlayerEnters() isn't triggered serversided, clientsided, or clientsided in gani scripts automatically when you warp a player to the same level he's already in. I shouldn't have to work around it either way.

Check for the level before warping. If the player is already in the same level, just change their x and y...?

Nobody ever should have to do anything that inconveniences them. What exactly is the problem with using your work-around?

You can redefine the setlevel2 function to do this (Do this in a player joined class for example). :]

Read my first post. :whatever:

Yeah sure, let's fix everything on our own instead of bringing it to Stefan's attention so he can fix it instead. Geez guys, show some more enthusiasm, this is obviously something that should be looked into since it's affecting the onPlayerEnters() triggers in the engine.

Ow, well. You know this won't be fixed within the next two years, though. Guess you gotta live with that workaround.

With that attitude it sure as hell wont. Damn, if you feel this way about Graal, just leave already, it's not like you're improving things with that attitude.

Won't improve things with any other attitude anyway, I've already learned that over the years.

Talk about lack of faith... x_x

Not to be argumentative, but the function name speaks for itself: it's called when a player enters a level, not when they move around in one.

If an engine doesn't do something exactly how you want it to, it's your job to find a way around that. Expecting the engine to be updated for your specific needs is fruitless.

That would be fine and all, if it weren't killing all attached ganis timeouts, which classifies it as a bug.

Barely. But, fine. You win.

I've not experienced this problem set, does it also happen with the trading card effects and pets?

I would debug it, but I don't have any cards at all, and buying them just to debug this sounds a bit too excessive even for me.