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

Teleport issue #53

Open
DominicDV opened this issue Feb 10, 2016 · 3 comments
Open

Teleport issue #53

DominicDV opened this issue Feb 10, 2016 · 3 comments

Comments

@DominicDV
Copy link

I have a multiserver setup, and use a different plugin for cross server teleportation.
When new players enter the server, and go through the portals they are back teleported to
the point they spawned (globalspawn), because their player data dont exists on the player they are connecting
Is it possible to add a flag to deactivate this behaviour?

EDIT: Tested it also with bungeeportals, portal type warp.
Some more info:
Tested in spigot and paperspigot
ForceAllPlayersToProxySpawn setting to true or on bungee false has no influence
Setting permode gesuit.spawns.new.server has no effect. ( I think it should teleport the player then to server spawn?)
how to reproduce: delete playerdata and stats in lobby and the destinationserver. Then join an go throuh the portals. It should teleport you back to the globylspawn of lobby
Edit 2: meaned gesuitportals instead bungeeportals

@Narimm Narimm added the on-hold label Feb 10, 2016
@Narimm
Copy link
Member

Narimm commented Feb 10, 2016

Plugin conflicts are not really geSuit issues. Unless you can show this is a bug or problem with geSuit I am closing the issue. We don't make any guarantees these plugins are compatible to use with other plugins, that replicate a function of geSuit.

@DominicDV
Copy link
Author

When removing all plugins (except gesuit, and the plugins it depends on) the problem persists.
Even when typing the normal /server [name] command I am back teleported to globalspawn. Same with /warp, or warp type portals or spawn type portals of geSuit. Note that this problem exists only the first time a player joins the portaldestination server (more specific when is uuid isnt in playerdata world folder). When deleting the geSuitSpawn module of the portal-destinationserver, this problem dont occurs.
Plugins in Bungeecord: gesuit + yamler 2.3.0
plugins at bukkitserver: [gesuitHomes, Portals, Spawn, Teleports, Warps (all latest builds)] Worldedit-bukkit-6.1 PermissionsEx-1.23.3.
Here some logs:
experiment 1
Fromserver (Portal type warp): http://pastebin.com/m51R3vqn
Toserver (Portal type warp): http://pastebin.com/jdCpbRxB
experiment 2
Fromserver Portal type spawn: http://pastebin.com/4E5yhQ2D
Toserver portal type spawn http://pastebin.com/b6ZxLUp1
bungeelog http://pastebin.com/cENEHRtn
EDIT:
before experiment 2 I changed
SpawnNewPlayerAtNewspawn: false
ForceAllPlayersToProxySpawn: false
and removed gesuit.spawns.new.server (permissions without the three .new possibilities)

@Narimm
Copy link
Member

Narimm commented Mar 31, 2020

Is this still an issue?

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

No branches or pull requests

2 participants