Stuck in stone when using IRIS

[Draxhax]

Scenario - shutdown_timeout is set to 0. Create two gates, one with an IDC and one without. Activate the gate without the IDC and use the /dial [idc] to open the other end. Go through the gate and end up getting stuck. About 90% of the time I end up getting stuck in rock or something else in the space below my stargate. This occurs only if my timeout is set to 0 or the person steps through as it reaches its timeout. Is there any way to set this up so that if there is an IRIS on the gate, to close either after the player steps out or maybe a delay to closing the destination?

[lycano]

shutdown_timeout 0 would result in having a gate nearly instant closed. It only stays open cause the animation takes time to render fully then closes. I would suggest you dont use a lower value than 5 for the shutdown as it could always be laggy situations where lower values may result in a wrong player placement.

Shure this case is by design cause the shutdown_timeout and player thread is seperate thus not meant to be dependend on each other. If the target gate has timeouted you should die when the IDC is active.

Anyhow i will see what i can do to prevent this.

[Draxhax]

One of the things I could think of is either an IDC close delay, or possibly have it detect that if the portal closes and the IDC is supposed to reactivate, detect if a player is standing in the space where the IDC would spawn the block, and simply not spawn the blocks until the player is out of the way (but still have the gate locked).

Unfortunately, I have not created any mods for minecraft servers so I am unsure of the feasibility of this request, but I have to say, this would probably fix the only thing I found to be a slight inconvenience. For the time though, I do have my shutdown_timeout set to 5 seconds.

[lycano]

well to be honest shutdown_timeout is not ment to be set lower than 5 ^^ cause you simply cant activate a gate and walk through it in 2 seconds cause you cant walk that fast ^^

[lycano]

no further comments since august

[Draxhax]

Sorry, I missed your response to mine. In your forum post for the mod, it states this:

/wormhole shutdown_timeout Setting to 0 means portal only closes after something goes through, and then immediately closes.

Therefore, my setting it to 0 is working as designed to allow me to wait and step through. I set it to 0 specifically because of people that are either lagging or have systems that aren't quite up to speed. Giving them time to walk through their gate without setting a specific amount of time.

[lycano]

Okay let me explain ^^

Forget about the post in bukkit forums.

What shutdown_timout 0 will do:

• instantly deactivate the gate after dialed.
• if you have a gate animation it will synchronously be visible on both sides and shutdown after finishing the animation

During that you have to hurry and walk through the gate while the animation is in progress. If you hit the event horizon not in time you will not be teleported cause the gate reached the status "deaktivated" cause of shutdown_timeout 0

shutdown timeout 0 also is completely seperated from users scope it doesnt check "a user has activated it before" it simply closes gates when no object is in the gate.

Depending on lag of server the Gate will remain open after the animation for a while ~ 50ms or so. Zero doesnt mean "wait till a player walk through"

Maybe there was a misunderstanding for this setting or i have to change the description but this is what it ever did or currently does ^^ If you have laggy clients then i would suggest setting it to above 5 or 10

10 is a good value for almost any situation where you want to have "fast closing gates"

EDIT: The reason why someone is stuck in the stone after stepping through a gate while having shutdown_timeout set to Zero is "activated iris comes back and cause of lag"