|
|
iirc even pi has support for attaching objects to tasks so checking is not needed, all tasks with the attached player will be stopped automatically when the player logs outOriginally Posted by Rhubarb
he doesn't seem to be attaching the player instance though lol
quoted lare's reply.
CycleEventHandler.getSingleton().stopEvents(this);
this is called in destruct, so it should be stopping the event if they disconnect
How come you don't just switch frameworks?
OT: Someone will probably use. Good job.
In logout method there's something like this:
CycleEventHandler.stopAllEvents(this);
so there's no need to add those extra checks
edit:
nvm already been told
The itemHandler is causing a dupe atleast for me? when i drop a item there appears 2 of them
08-14-2014, 07:11 AM
why did you bump a year+ old thread, with the most recent reply being almost a year ago? Oh, and for you issue, re-add what you removed 1 by 1 until you fix your issue; if you re-add what you deleted then it isn't from your cleaning duties.
Didn't check the posting area of the thread and its been resolved forgot to remove something
Bump, I know this is 2 years old, but still worth doing.
been adding / modifying these / using as a template for my own process clean up, I think more servers should use them.
| « Perfect Title System [Full Support] | [PI] Improvements - Cleaning/Converting Process to Events. » |
| Thread Information |
Users Browsing this ThreadThere are currently 1 users browsing this thread. (0 members and 1 guests) |
