0001762: @Mount -> @Dismount - SphereServer BugTracker

(0000672)
babidi (reporter)
23-09-10 19:52
edited on: 23-09-10 19:52

it makes sense
build #1333 still not resolved

(0000692)
Coruja (developer)
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 (reporter)
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 (reporter)
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 (developer)
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 (reporter)
15-12-13 01:33

thanks for "quick fix")

sarcasm.

already fixed it by scripts.

(0001849)
khaos (developer)
15-12-13 08:24

Fixed. Dismount will now call before the mount on Chars.

Issue History
Date Modified	Username	Field	Change
09-06-10 16:40	HOCOK	New Issue
09-06-10 16:40	HOCOK	Nightly Version	=> Not Available
09-06-10 16:40	HOCOK	Experimental Flags	=> None
09-06-10 16:40	HOCOK	Option Flags	=> None
23-09-10 19:52	babidi	Note Added: 0000672
23-09-10 19:52	babidi	Note Edited: 0000672	View Revisions
07-10-10 04:42	Coruja	Note Added: 0000692
07-10-10 07:47	babidi	Note Added: 0000693
14-11-10 19:54	MrSugarCube	Category	executable - linux => executable - linux build
11-02-11 09:21	trinax	Note Added: 0000903
11-02-11 09:23	trinax	Note Edited: 0000903	View Revisions
11-02-11 09:24	trinax	Note Edited: 0000903	View Revisions
15-12-13 00:21	khaos	Note Added: 0001846
15-12-13 00:21	khaos	Assigned To	=> khaos
15-12-13 00:21	khaos	Status	new => feedback
15-12-13 01:33	HOCOK	Note Added: 0001848
15-12-13 01:33	HOCOK	Status	feedback => assigned
15-12-13 08:24	khaos	Note Added: 0001849
15-12-13 08:24	khaos	Status	assigned => resolved
15-12-13 08:24	khaos	Fixed in Version	=> 0.56c Nightly
15-12-13 08:24	khaos	Resolution	open => fixed

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

(0000692) Coruja (developer) 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 (reporter) 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 (reporter) 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 (developer) 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 (reporter) 15-12-13 01:33	thanks for "quick fix") sarcasm. already fixed it by scripts.

(0001849) khaos (developer) 15-12-13 08:24	Fixed. Dismount will now call before the mount on Chars.

Relationships