Troubleshooting DarkSpawn When the Teleport Fails

Check the Basics First

Confirm you typed /trigger darkspawn exactly. Confirm the server actually has the mod loaded — if it was removed or failed to start, the trigger will not exist. Try the command in a different dimension; some setups only enable it in the overworld.

Common Causes

If the command runs but you do not move, you may already be at the destination. If you get an error about an unknown objective, the scoreboard trigger has not been initialized — this usually means the datapack did not load. Run /reload and try again. If you are teleported but then immediately fall or suffocate, the destination coordinates are wrong: the Y value is too high, too low, or inside a block. Only an admin can fix that by editing the datapack file.

When It Is a Server-Side Problem

Because the mod lives entirely on the server, client-side issues are rare. If one player can teleport and another cannot, compare their permissions and whether they are in the same world. If nobody can teleport, the datapack file is likely missing, corrupted, or pointing at a dimension that no longer exists. Ask the admin to verify the file and reload.

Reporting to Your Admin

Tell them the exact error message, your current dimension, and your coordinates. That is enough for them to check the destination values and the dimension identifier in the datapack.