@PersonalSpace trigger malfunctioning about source-x HOT 8 OPEN

What version of sphere you used?
This was touched on last commit cad5459#diff-e1ae3608ed3c89cae2f5c81d003b6a1eb1b38b9313e6ccae97fd96b106c27e6e

from source-x.

What version of sphere you used? This was touched on last commit cad5459#diff-e1ae3608ed3c89cae2f5c81d003b6a1eb1b38b9313e6ccae97fd96b106c27e6e

Compiled at Jun 14 2024 (21:17:53) [branch master / build 3752 / GIT hash 8e44484]

from source-x.

Right now, the lane marked in red causes any attempt to fail if stam is lesser than maxstam.
This means any custom script will need to do what u did. Set argn=0 to always allow step and then use your own system to allow or deny.
If argn is not set 0, only chars at maxstam will step.

Can be changed, but I see no real drama to let it be as it is cos u can set ur own custom system. But I can agree it is confusing.

from source-x.

Could you try to set this to 1 and test again?

from source-x.

Could you try to set this to 1 and test again?

Im using this setting already

from source-x.

we should add a local.AllowifStamIsLowerThanMaxStam or another sphere.ini config for it. Whatever u decide I can try.

from source-x.

we should add a local.AllowifStamIsLowerThanMaxStam or another sphere.ini config for it. Whatever u decide I can try.

I cant make that decision, thats up to devs.
I only know that we can make workaround, but the trigger is useless as it is now. Without argn1=0 you cant do anything, and still argn2 doesnt do anything either way. 😶

from source-x.

the trigger is not useless but I agree with you that there should be a way to bypass that behaviour. I think a local.bypassStam should do the job.
Whatever U (the community) decide I can try.

MAybe we could remove the check I marked in red, and include that check on the sphere-x scriptpack instead source.

from source-x.