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

Spawn and Warp bug in other dimensions #1344

Closed
Wirelli opened this issue Apr 10, 2019 · 8 comments

Comments

Projects
None yet
5 participants
@Wirelli
Copy link

commented Apr 10, 2019

The issue
When a player goes into a dimension, like the nether, and does spawn, they're not returned to the overworld spawn, any idea on how to fix this, if its not a bug. It's the same with /warp

Nucleus Version
1.9.1-S7.1

SF Version
1.12.2-2768-7.1.6-RC3640

Nucleus Info
https://gist.github.com/dualspiral/5b875c738efe0222480b9bb57cb62659

To Reproduce
Steps to reproduce the behavior:

  1. Go to 'The nether dimension'
  2. Do /spawn(set in overworld) or /warp (warp set in overworld)
  3. See error

Expected behavior
You will be sent to the same cords, but in the nether(or any other dimension tested in)

Log
https://gist.github.com/Wirelli/d455854f4f0b2415cd4f8d004d63b0e4

@dualspiral

This comment has been minimized.

Copy link
Member

commented Apr 10, 2019

For spawn, it's by design, it'll send you to the spawn point of the world you're in by default. Read https://nucleuspowered.org/docs/modules/spawn.html which explains how to get the behaviour you're looking for.

As for /warp, considering that's effectively a named location thing, running /warp on its own won't do anything. I do not even see it in your logs. However, I notice the plugin Nations there... I don't think that actually works properly any more so that might be the problem anyway...

@dualspiral

This comment has been minimized.

Copy link
Member

commented Apr 16, 2019

It's interesting that someone else in discord had this issue too - it might be related to the modpack...

@Yorkforce

This comment has been minimized.

Copy link

commented Apr 22, 2019

Confirming were having this issue too.
We did the /setworldspawn and /setspawn commands for 256x256, checked the level.dat file for the world and its definitely set to 256x256 but if a player dies in another dimension or uses a teleport cake (telepastries mod in SF4) they respawn at 2x2, the original spawn point of the world.

I guessing a mod in the pack is setting its own spawn point and overriding the level.dat for some strange reason.

If anyone manages to figure out which mod is doing it I would be very grateful, it's hard to track down in a modpack with 212 mods.

@dualspiral

This comment has been minimized.

Copy link
Member

commented Apr 22, 2019

I’d be grateful too! It’s not a Nucleus issue by the looks of this, but something is being weird...

@Yorkforce

This comment has been minimized.

Copy link

commented Apr 22, 2019

Actually sorry, this might purely be a telepastries mod issue were having and not related to this issue.

If a player dies they return to thier bed and/or home, seems to be just the teleport cakes.

EDIT: Nope, there is something odd going on.
Using /spawn in nether drops you at 2x2
Using /is spawn does same
Using /is home (skyclaims nucleus override) does same

2x2 was the very first location the world started with so something it setting that and ignoring world spawn/homes etc

@kencinder

This comment has been minimized.

Copy link

commented Jun 7, 2019

This is caused by, and is by design, with the Topography mod in SF4.

For example, with dirt_tree type.

SF4.registerDimension(0, "SF4/dirt_tree")
SF4.registerDimension(-1, "SF4/nether/nether_cell")
SF4.addInitialPlayerFunction("triumph:start_standard")
SF4.disableNetherPortal()

In dirt_tree dimension config is captureTeleports()

captureTeleports: Notes: If this dimension has a spawn structure set, then when teleporting to the dimension, this option cancels the dimension change and has Topography transfer the player itself, placing them in the spawn position on the spawn structure.

So really if you want to stop it, remove that line from config/topography/SF4/dirt_tree.txt and restart the server. Or substitute dirt_tree for whatever SF4 world type you're using. It appears that would be changing the way the pack is intended to work mind you.

@dualspiral

This comment has been minimized.

Copy link
Member

commented Jun 7, 2019

You'd hope that this would be documented as part of the pack...

Anyhow, I'll close this as it's something else taking over.

@dualspiral dualspiral closed this Jun 7, 2019

@ktole1999

This comment has been minimized.

Copy link

commented Jun 7, 2019

This is caused by, and is by design, with the Topography mod in SF4.

For example, with dirt_tree type.

SF4.registerDimension(0, "SF4/dirt_tree")
SF4.registerDimension(-1, "SF4/nether/nether_cell")
SF4.addInitialPlayerFunction("triumph:start_standard")
SF4.disableNetherPortal()

In dirt_tree dimension config is captureTeleports()

captureTeleports: Notes: If this dimension has a spawn structure set, then when teleporting to the dimension, this option cancels the dimension change and has Topography transfer the player itself, placing them in the spawn position on the spawn structure.

So really if you want to stop it, remove that line from config/topography/SF4/dirt_tree.txt and restart the server. Or substitute dirt_tree for whatever SF4 world type you're using. It appears that would be changing the way the pack is intended to work mind you.

we had to do this in order to get skyclaims to work properly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.