SphereServer BugTracker - SphereServer
View Issue Details
0001762SphereServerexecutable - linux buildpublic09-06-10 16:4015-12-13 08:24
HOCOK 
khaos 
normalminoralways
resolvedfixed 
0.56c Nightly 
0.56c Nightly 
Not Available
None
None
0001762: @Mount -> @Dismount
Incorrect work.

How it work now:

When you sit on horse, and you dclick on another horse

1. Triggering @Mount
2. Triggering @Dismount

How it should work:

1. Triggering @Dismount
2. Triggering @Mount

Because if you will set tag on @Mount , the tag will be immediately removed in @Dismount (Core bug)
No tags attached.
Issue History
09-06-10 16:40HOCOKNew Issue
09-06-10 16:40HOCOKNightly Version => Not Available
09-06-10 16:40HOCOKExperimental Flags => None
09-06-10 16:40HOCOKOption Flags => None
23-09-10 19:52babidiNote Added: 0000672
23-09-10 19:52babidiNote Edited: 0000672bug_revision_view_page.php?bugnote_id=0000672#r27
07-10-10 04:42CorujaNote Added: 0000692
07-10-10 07:47babidiNote Added: 0000693
14-11-10 19:54MrSugarCubeCategoryexecutable - linux => executable - linux build
11-02-11 09:21trinaxNote Added: 0000903
11-02-11 09:23trinaxNote Edited: 0000903bug_revision_view_page.php?bugnote_id=0000903#r111
11-02-11 09:24trinaxNote Edited: 0000903bug_revision_view_page.php?bugnote_id=0000903#r112
15-12-13 00:21khaosNote Added: 0001846
15-12-13 00:21khaosAssigned To => khaos
15-12-13 00:21khaosStatusnew => feedback
15-12-13 01:33HOCOKNote Added: 0001848
15-12-13 01:33HOCOKStatusfeedback => assigned
15-12-13 08:24khaosNote Added: 0001849
15-12-13 08:24khaosStatusassigned => resolved
15-12-13 08:24khaosFixed in Version => 0.56c Nightly
15-12-13 08:24khaosResolutionopen => fixed

Notes
(0000672)
babidi   
23-09-10 19:52   
it makes sense
build #1333 still not resolved

(0000692)
Coruja   
07-10-10 04:42   
Maybe not, its a logical condition

You're on a house, if you try to mount on another horse (@Mount) you can call return 1 to prevent mounting this new house because youre already mounted.
This will be not possible if you dismount calling @Dismount after call @Mount again because you will never be mounted when @Mount got called
(0000693)
babidi   
07-10-10 07:47   
yes you're right
but we have to find a solution for this
because of those who don't wants to disable the feature of "jumping" from a horse to another but however they want their scripts works properly.

is it logical to say if you are on a horse and want to mount on another you have to dismount first (@dismount) and then mount to the second (@dismount)

i'm shure there is a way to prevent mounting a horse if you are mounted and making @dimount and then @mount toghether.
(0000903)
trinax   
11-02-11 09:21   
(edited on: 11-02-11 09:24)
You can check if you are already mounted on @Mount instead of needing Dismount to be cast before Mount with a simple if statement and remove your tags or whatever there IMO.

But changing their order will remove the chance to prevent jumping between horses, you will have to unmount even if you prevent mounting to another.

It should not change, you can manage your scipts to work properly but changing the order will decrease the ways of usage of two triggers.

(0001846)
khaos   
15-12-13 00:21   
I committed a possible fix tonight. It should be available tomorrow night. Let me know if it works or not. There is now a check to see if the player is mounted when trying to mount again and calls DISMOUNT before allowing the action.
(0001848)
HOCOK   
15-12-13 01:33   
thanks for "quick fix")

sarcasm.

already fixed it by scripts.
(0001849)
khaos   
15-12-13 08:24   
Fixed. Dismount will now call before the mount on Chars.