-
Notifications
You must be signed in to change notification settings - Fork 63
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Halt train before teleport until destination is free of trains #466
Comments
I can probably add a syntax to make multi-world linking of mutexes work. No technical reason why it cant work |
My trains don't even teleport now, and I get this in the log:
This is with multiverse-portals. Train_Carts: v1.20.1-v3-SNAPSHOT (build: 1444) |
Did multiverse portals actually enable properly? Can you check the server log whether it enabled prior? EDIT nvm I see what went wrong, give me a moment |
This should fix it. I broke it when I rewrote that logic using SoftDependency api. https://ci.mg-dev.eu/job/TrainCarts/1450/ (Should add that the main issue isnt fixed yet or implemented of course) |
thanks for the swift response! I'll give that a spin when I can restart server and report back (sorry to hijack this issue!) |
confirmed, teleport to portal working again (without mutex) |
Info
Please provide the following information:
/train version
): v1.19.3-v2-SNAPSHOT (build: 1288)/train version
): v1.19.3-v2-SNAPSHOT (build: 1453)/version
): git-Paper-39 (MC: 1.19)Bug
Description
Using a teleport sign to teleport trains to a multiverse portal in another world doesn't check whether the rail is free at the destination. If a train is stuck (due to other bugs I haven't pinned down), this can cause trains to all land on top of one another and make a mighty laggy mess at the destination. Named mutexes don't work between worlds so can't help.
Expected behaviour
It'd be great if they slowed down and queued up at the teleport sign until there was enough space at the destination for the train to teleport. This would tail back but would prevent more trains from spawning as train spawners appear to have logic to prevent spawning when a train is already stuck waiting there.
Actual behaviour
The trains teleport regardless of the condition at the other end (though I have known for trains to end up broken before the teleport, but I think thats due to pushing around at the destination and ending up teleporting back the other way).
Steps to reproduce
Additional Information
This is a follow on from issue #460
The text was updated successfully, but these errors were encountered: