Skip to content
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

Duplicated portal in forge multi-server #1424

Closed
3 tasks done
Evenstarneko opened this issue Dec 23, 2021 · 1 comment
Closed
3 tasks done

Duplicated portal in forge multi-server #1424

Evenstarneko opened this issue Dec 23, 2021 · 1 comment
Labels

Comments

@Evenstarneko
Copy link

Forge Version

36.2.19

Twilight Forest Version

4.0.546

Client Log

No response

Crash Report (if applicable)

No response

Steps to Reproduce

  1. Use a forge multi player server and join more than 2 players
  2. I am not sure if this only happens when delay time is long. In my case some players have 400ms+ delay.
  3. One of the player open the portal and join, everything is fine.
  4. Another player join the same portal some time later, there is a chance (My experience is roughly 10%) that A new portal will be created, and the location is in some forbidden area (like Fire Swamp) and he receives debuff.
  5. When that player try to go back using the new portal, it will create another portal in the main world, which is always deep inside some caves.
  6. Two portals in main and two portals in twilight forest have the same relative distance.

What You Expected

Different player join the same portal should be ported to the same place in twilight forest, and it should not be in some forbidden areas.

What Happened Instead

In my case there is a chance that a second user of the portal will be proted to a new location and likely in a forbidden area. When they come back another new portal in main world will be created. A total of 6 new portals are now exist in my server in two days of playing.

Additional Details

I am not using Optifine or other bug-related things.

Please Read and Confirm The Following

  • I have confirmed this bug can be replicated without the use of Optifine.
  • I have confirmed the details provided in this report are concise as possible and does not contained vague information (ie. Versions are properly recorded, answers to questions are clear).
  • I have confirmed this issue is unique and has not been reported already.
@GizmoTheMoonPig
Copy link
Member

redirecting this to #1459 so we can keep track of every portal issue in 1 place

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants