cam does not remember dimension you went into cam with

[hannafoxie]

i was experiencing a cam bug where it would remember the coordinates i went into spectator in but not the dimension so i reinstalled the script and encountered this bug #377 so i changed the script as per the fix by petersv5 and that fixed bug 377 but now it still doesnt return you to the original dimension making using the script really annoying

carpet ver: fabric-carpet-1.19.4-1.4.101+v230319.jar
Minecraft ver: fabric-carpet-1.19.4-1.4.101+v230319.jar

server side mods:

additional context: "cam.sc" is renamed to "c.sc"

[rv3r]

Can you tell me more about how to reproduce this and exactly what the problematic behavior is? I'd like directions like stand here, be in this dimension, change to spectator mode, etc, and that I should expect to be in the wrong position, wrong dimension, or whatever happens. I can't seem to reproduce this at the moment, so I won't be able to help until then.

[hannafoxie]

Can you tell me more about how to reproduce this and exactly what the problematic behavior is? I'd like directions like stand here, be in this dimension, change to spectator mode, etc, and that I should expect to be in the wrong position, wrong dimension, or whatever happens. I can't seem to reproduce this at the moment, so I won't be able to help until then.

tbh I don't how know to reproduce the issue, but no matter what dimension you are in when you go into spectator or where in that dimension you are it does not remember the dimension you was in when you went into spectator so you get put at the coordinates you entered but in the dimension that you leave spectator (say if you are in the overworld and go into spectator to look at someone who is in the nether you will be put into the nether yourself at your overworld coordinates)

[rv3r]

Okay now I understand. I didn't think to test that behavior in singleplayer, so I'll mess around with that later and I should be able to fix it. Thank you for the added detail.

[hannafoxie]

Okay now I understand. I didn't think to test that behavior in singleplayer, so I'll mess around with that later and I should be able to fix it. Thank you for the added detail.

was this bug ever fixed or did you ever find out what caused It to happen?