-
Notifications
You must be signed in to change notification settings - Fork 209
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
Wayback Nether portal problems #144
Comments
Can confirm this with build 1.9.10(beta) and paper build git-paper-96 |
Yeah lots of people are reporting this bug, author is not responding :( |
Bugs with teleporting from nether to overword via Portals... Bug 1: Bug 2: |
@Leonardo-Fiori I was the original poster of the image that image. I have created new issue #145 it has the whole map rendered and the map has these squares quite often as the distance from the spawn increases. |
@Brettflan , where are you! |
Im posting also here, to keep this issue updated. The original post is from another similar issue, to which @Brettflan answered that it is spigot fault, and not worldborder's fault. This is the proof that he is wrong. I just expanded the map, now i have set the overworld to 2000 blocks using /wb set 2000. 2000/250 = 8, the magic number for nether portals. When i go from the nether to the overworld using the same portal that i got teleported to when coming from the overworld, it says: You have reached the edge of this world, and it teleports me far away inside the map! AS SOON AS I DISABLE WORLDBORDER, if i try again to do the same thing with the SAME portals, if i go to the nether it still teleports me to the same (correct) portal, but when i COME BACK, it does not say that i have reached the edge of the world, and it teleports me to a correct portal, that is INSIDE the edge of the world and near to the one i started from. (The portal in the nether was not exactly at the starting coords / 8 so when it multiplied the coords by 8 it teleported me to a slightly different location, but still correct and inside the 2000 blocks border). Just say what you want, that is spigot fault, but if i keep your (still awesome) plugin disabled, the nether portals are working correctly. As soon as i enable it, they get screwed up. Think about it. P.s. i reported it to spigot and they said that the problem is caused by the WorldBorder plugin |
i have seen that when i activate worldborder bypass the portals are working without any problem |
Of course, but players then are allowed to walk beyond the border.. so whats the point of this plugin then? :( |
Thnx @JonMagon going to check and test it out |
The problem isn't at all with nethers portals. It's issue with all world-to-world teleportations if worlds have different radius and you're very far from world spawn. I've disabled all teleportation events and it works good, players can't pass border. Not final solution, but for a while now. |
Any news on a fix? |
@JohnS19 for now just enable worldborder when you need to fill/trim then use vanilla wolrd border |
Looks like a duplicate of #131. |
It looks like they finally fixed it: So it should hopefully be handled in the next Spigot release. |
I'm not the only one here having this problem..
when players go to the nether using a portal that is near the overworld border, they get teleported correctly to the nether. But when they use the portal that has just spawned in the nether to get back to the overworld, they get teleported wayy beyond the overworld border, and then slingshotted back to the center of the map, causing lots of lag (and angery)
Happening both on latest version of spigot and paper
Then there is another problem. If you expand the overworld border and then to a /fill, worldborder fails to fill a "ring" of chunks just after the original map size.. another player reported this on the spigot forums, he made a screenshot. I did forget to make a screenshot and proceeded filling the chunks manually by flying over them. Here is the screenshot:
https://proxy.spigotmc.org/bcf716a501192b862c8d2d85e72f8e546286d375?url=https%3A%2F%2Fi.imgur.com%2FLqiWadN.png
The text was updated successfully, but these errors were encountered: