mojira.dev

SamtheBKBoss

Assigned

No issues.

Reported

MC-244781 /locate and Eye of Ender and pointing to nonexistent strongholds in upgraded chunks Duplicate

Comments

Can confirm in 1.19-pre3.

Affects 22w17a.

It also seems like this happens when I have them on a lead held by myself.

@Gnembon Wasn't expecting a Mojang response on my random comment... thanks for the insight! For structure files, I assume the fix is the same for MC-249450?

Affects 22w16b.

Correction from my previous comment: sensors generated in custom structures are slightly different from those in superflat worlds. In superflat worlds, they begin working like normal after being stepped on by any mob once, whereas in structures, they work when stepped on, but NEVER resume normal ranged functionality.

To be honest, I could totally see the developers making superflat sensors work like this on purpose so as to not overload the game with sensor activation on world generation. 

The issue is different now. Sculk Sensors generated in a standard or single-biome world work perfectly. This issue only applies to superflat worlds, as well as Sensors generated as part of a custom structure. In these specific cases, as of 22w15a, the sensors had "sculk_sensor_phase" set to "inactive," not "cooldown," but they still don't quite work until an entity steps on them. As soon as they're stepped on, they work perfectly again.

Can confirm for 1.18.2 and 22w15a.

Can confirm in 1.18.2 and 22w15a.

Can confirm in 1.18.1, per my duplicate report

@Brent Wrong. This bug pertains specifically to the upgrading of old worlds, whereas that one deals with the inaccuracy of /locate in general. I would consider this a Duplicate of #MC-135996.

D E, in the third bug it's explicitly stated that the game is pointing the player to chunks that haven't been generated yet, so I don't know what's up with that, but the other two are definitely related. Truly sad.

Dhranios, dang that's an old issue. That's probably what this is a duplicate of. It was rather difficult to find bugs on this topic. Didn't know it affected older versions.

This was my first bug report, what do I do now? Should I (or can I) close the report myself? Do I need to wait for a mod to report it as duplicate?

Confirming for 1.17.1

Can confirm in 1.17 Release Candidate 1.

Can confirm for 1.17 Release Candidate 1.

Can confirm for 1.17 Release Candidate 1.

Can confirm in 1.17 Release Candidate 1. By the way, this also applies to redstone torches. Looks like that last remark is already reported as MC-141297. Sorry, it's really hard to find bugs on blockstates for some reason.

Can confirm in 1.17-rc1.