Page 1 of 1
Two event suggestions
Posted: Tue Jul 06, 2004 3:19 pm
by Galbuu
I'd love to see these two events in a future version of UOX3.
onMount(pMounter, pMounted)
Attached to rideable creatures to do effects.
onTime(time)
Would run when time is reached.
Posted: Tue Jul 06, 2004 4:33 pm
by Xuri
Or even attached to player chars to do effects when they mount whatever

Posted: Tue Jul 06, 2004 4:57 pm
by Galbuu
Xuri wrote:Or even attached to player chars to do effects when they mount whatever

Well attaching them to creatures gives more customizeability (is that a word?), because then you can give penalties/bonuses based on creature.
Posted: Tue Jul 06, 2004 5:00 pm
by Xuri
You could do that independently of which object the script was attached to, as long as both the playercharacter and the mount-character are provided as arguments in the event header.
Posted: Wed Jul 07, 2004 2:52 am
by Maarc
You wouldn't need an onTime event if you had an onMountStatus( on/off ), as you could create a timer loop from within that, if you really wanted to.
There might be a way of doing what you want anyway.... create a script for mountable NPCs, there might be a way to override the onUse event (or hook up the plumbing for it) so that would become the onUse event. You'd have to take care of the mounting responsibilities. You'd have to attach an unmount script to the created mount (which is an item, not character), and override it's onUse script to do the switcheroo again.
Posted: Thu Jul 08, 2004 4:02 am
by Galbuu
You must've misread what I want from the onTime function. It would be part of UOX's scripts or something and whenever time is reached the script would run. The reason I want this is for my food calorie system (to set calories to 0 in the morning and do appropriate effects).
Posted: Thu Jul 08, 2004 6:49 am
by Maarc
I had the thought that the two of them were related, I didn't see a difference.
However, I still don't see the need for an onTime event like you suggest. You could easily achieve that through using a StartTimer from within another event which would set it all off (eg from onLogin for an PC). Ultimately, you're still having to start the onTime event somehow (we can't magically divine the end time from nowhere), so all the functionality already exists.