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

NPCs teleporting but not spawning when using /npc tphere from a long distance #2074

Open
Elric02 opened this issue Mar 23, 2020 · 9 comments
Open

Comments

@Elric02
Copy link

@Elric02 Elric02 commented Mar 23, 2020

When teleporting a NPC from a location far away using /npc tphere, the NPC won't be visible until I disconnect and reconnect to the server, or reload the plugin. If I teleport to the npc using /npc tp while he isn't visible, it teleports me to his new correct location, the one after i did /npc tphere. So coords are updated but the npc does not get loaded.

The output of command /version on my server is:
PaperSpigot 1.15.2 version 143
The output of command /version citizens on my server is:
2.0.26 build 1852

@mcmonkey4eva

This comment has been minimized.

Copy link
Member

@mcmonkey4eva mcmonkey4eva commented Mar 24, 2020

Confirmed and replicated.

Running on Spigot instead of Paper, git-Spigot-6de3d4b-a6f8093 (MC: 1.15.2)

Tested as described - create NPC, went far enough away that it despawned, then used /npc tphere... it teleported but did not spawn until I reloaded the area (by reconnecting) to force it to.

Debug logs for later reference:

mcmonkey4eva[/127.0.0.1:57289] logged in with entity id 142 at ([world]-123.80894943477618, 64.0, -107.15271167252754)
mcmonkey4eva issued server command: /npc create bob
Fetched profile d664f4b4-d688-4d28-9fbd-3d58ef2844b4 for player Bob
Removing 167 from skin tracker due to DespawnReason.PENDING_RESPAWN
Despawned 167 DespawnReason.PENDING_RESPAWN
mcmonkey4eva issued server command: /npc tphere
mcmonkey4eva lost connection: Disconnected
mcmonkey4eva left the game
Removing 167 from skin tracker due to DespawnReason.CHUNK_UNLOAD
Despawned 167 DespawnReason.CHUNK_UNLOAD
Despawned id 167 due to chunk unload at [-24,-6]
mcmonkey4eva[/127.0.0.1:57300] logged in with entity id 278 at ([world]-373.6347583008354, 68.0, -77.57048536049129)
Spawned id 167 due to chunk event at [-24,-6]
@mcmonkey4eva mcmonkey4eva changed the title NPCs not teleporting when using /npc tphere from a long distance NPCs teleporting but not spawning when using /npc tphere from a long distance Mar 24, 2020
@Andre601

This comment has been minimized.

Copy link
Contributor

@Andre601 Andre601 commented Mar 27, 2020

I have an issue, that may be related to this in a way, which is, that the yaw of the player is ignored when running /npc tphere
The pitch and location seem to be updated but the yaw is for whatever reason ignored and seems to default to 0. (looking south)

This wasn't the case with the version prior to the current release (2.0.26) and even manually editing the yaw and pitch in the save.yml (while the server is offline of course) also seems to have no effect on this.

Versions:
Server: git-Paper-146 (MC: 1.15.2)
Citizens: 2.0.26-SNAPSHOT (build 1854)

@fullwall

This comment has been minimized.

Copy link
Member

@fullwall fullwall commented Mar 27, 2020

@Andre601 I have pushed a new build for you (separate to this issue)

@fullwall

This comment has been minimized.

Copy link
Member

@fullwall fullwall commented Mar 27, 2020

Try the latest build

@Andre601

This comment has been minimized.

Copy link
Contributor

@Andre601 Andre601 commented Mar 27, 2020

Receiving NPEs for latest build (1856)
https://paste.helpch.at/opeqemunuv.md

@fullwall

This comment has been minimized.

Copy link
Member

@fullwall fullwall commented Mar 27, 2020

Apologies, try 1857

@Andre601

This comment has been minimized.

Copy link
Contributor

@Andre601 Andre601 commented Mar 27, 2020

Can confirm that the yaw issue has been fixed with this build 👍

@fullwall fullwall closed this Apr 6, 2020
@mcmonkey4eva mcmonkey4eva reopened this Apr 6, 2020
@mcmonkey4eva

This comment has been minimized.

Copy link
Member

@mcmonkey4eva mcmonkey4eva commented Apr 6, 2020

This issue isn't fixed, the random second issue that Andre put inside this issue instead of separate is all that was fixed.
(For future reference, Andre: if it's not the same issue, make a separate issue post... "related" doesn't mean "same")

@Andre601

This comment was marked as disruptive content.

Copy link
Contributor

@Andre601 Andre601 commented Apr 6, 2020

I'm sorry that someone else thought this was in any way fixed, instead of waiting for the author to respond.
Please find someone else to blame, thank you very much.

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

Successfully merging a pull request may close this issue.

None yet
4 participants
You can’t perform that action at this time.