Minecraft Username: konan200x
Brief Description: /back command does not work when used right after /spawn
Instructions:
1. Go to Spot A (can be any).
2. Then tp to Spot B (can be any).
3. Use /spawn command.
4. Once at spawn, use /back.
5. You end up at Spot A instead of Spot B.
How many times did you recreate this bug?: two times
Result: Using /back right after /spawn skips a previous tp event.
Expected Result: I expected /back to tp me to the place at which I had used /spawn command.
Evidence: N/A
Thread Tools
Thread Tools
-
-
Agree x 1 - List
-
-
kukelekuuk C͕̹̲̽ͪ͐ͩ̔L̜̦̝͈ͦ̿̾̿ḘA̻̗̤̳̐ͭ̆̿̃̑ͭN̊̓͑̇ͯBuilder ⛰️ Ex-EcoLeader ⚜️⚜️⚜️ Premium Upgrade
That's because they're 2 different plugins that don't hook in/interact with each other. Maybe KHobbits can think of a way to fix it.
-
Sounds like the same thing that happened here: http://ecocitycraft.com/forum/threads/bug-report-unregistering-back-with-wild.86238/
-
kukelekuuk00 - https://github.com/essentials/Essentials/blob/2.x/Essentials/src/config.yml#L402
Needs tested to make sure it doesn't allow /back into sg if enabled, could also cause oddness with stargate teleports. -
I've found that an easy fix to this is just doing /warp risignspawn or legacyspawn depending on where you want to go.