Joseph
- SomeRandomUser
- JIRAUSER491368
- Europe/Stockholm
- Yes
- No
MC-185417
Bug
On a map with many maps in item frames, many of them reset upon updating to 20w21a from 20w20b. Taking the map out of the item frame creates a new map zoomed out to the maximum based on the current location. This did not happen with a few of the maps, as can be seen in the screenshots attached. These maps were created using an online map creator and skip several numbers and were placed in the newly added invisible item frames.
How to reproduce
- Have a world with maps in item frames
- Update it to 20w21a
Most maps in item frames disappear
Logs
The logs have many entries like the following that seem to be related to the problem
[01:55:56] [Server thread/ERROR]: Not a string
[01:55:56] [Server thread/ERROR]: Error loading saved data: map_310011
java.lang.IllegalArgumentException: Invalid map dimension: 0b
at cyt.c(SourceFile:126) ~[20w21a.jar:?]
at cyt$$Lambda$4189/1620636011.get(Unknown Source) ~[?:?]
at java.util.Optional.orElseThrow(Optional.java:290) ~[?:1.8.0_51]
at cyt.a(SourceFile:126) ~[20w21a.jar:?]
at cyy.c(SourceFile:72) [20w21a.jar:?]
at cyy.b(SourceFile:58) [20w21a.jar:?]
at yw.a(SourceFile:1159) [20w21a.jar:?]
at bjt.a(SourceFile:59) [20w21a.jar:?]
at bjt.b(SourceFile:64) [20w21a.jar:?]
at yv.a(SourceFile:94) [20w21a.jar:?]
at yi.g(SourceFile:1070) [20w21a.jar:?]
at yu.p(SourceFile:398) [20w21a.jar:?]
at yu.a(SourceFile:337) [20w21a.jar:?]
at yw.a(SourceFile:347) [20w21a.jar:?]
at net.minecraft.server.MinecraftServer.b(SourceFile:893) [20w21a.jar:?]
at net.minecraft.server.MinecraftServer.a(SourceFile:832) [20w21a.jar:?]
at enr.a(SourceFile:89) [20w21a.jar:?]
at net.minecraft.server.MinecraftServer.run(SourceFile:691) [20w21a.jar:?]
at java.lang.Thread.run(Thread.java:745) [?:1.8.0_51]
Bug
On a map with many maps in item frames, many of them reset upon updating to 20w21a from 20w20b. Taking the map out of the item frame creates a new map zoomed out to the maximum based on the current location. This did not happen with a few of the maps, as can be seen in the screenshots attached. These maps were created using an online map creator and skip several numbers and were placed in the newly added invisible item frames. The correct .dat files for the map are still in the game folder.
How to reproduce
- Have a world with maps in item frames
- Update it to 20w21a
- Try to use commands to give the filled map, e.g. /give @a minecraft:filled_map{map:103}
Logs
The logs have many entries like the following that seem to be related to the problem
[01:55:56] [Server thread/ERROR]: Not a string
[01:55:56] [Server thread/ERROR]: Error loading saved data: map_310011
java.lang.IllegalArgumentException: Invalid map dimension: 0b
at cyt.c(SourceFile:126) ~[20w21a.jar:?]
at cyt$$Lambda$4189/1620636011.get(Unknown Source) ~[?:?]
at java.util.Optional.orElseThrow(Optional.java:290) ~[?:1.8.0_51]
at cyt.a(SourceFile:126) ~[20w21a.jar:?]
at cyy.c(SourceFile:72) [20w21a.jar:?]
at cyy.b(SourceFile:58) [20w21a.jar:?]
at yw.a(SourceFile:1159) [20w21a.jar:?]
at bjt.a(SourceFile:59) [20w21a.jar:?]
at bjt.b(SourceFile:64) [20w21a.jar:?]
at yv.a(SourceFile:94) [20w21a.jar:?]
at yi.g(SourceFile:1070) [20w21a.jar:?]
at yu.p(SourceFile:398) [20w21a.jar:?]
at yu.a(SourceFile:337) [20w21a.jar:?]
at yw.a(SourceFile:347) [20w21a.jar:?]
at net.minecraft.server.MinecraftServer.b(SourceFile:893) [20w21a.jar:?]
at net.minecraft.server.MinecraftServer.a(SourceFile:832) [20w21a.jar:?]
at enr.a(SourceFile:89) [20w21a.jar:?]
at net.minecraft.server.MinecraftServer.run(SourceFile:691) [20w21a.jar:?]
at java.lang.Thread.run(Thread.java:745) [?:1.8.0_51]
Bug
On a map with many maps in item frames, many of them reset upon updating to 20w21a from 20w20b. Taking the map out of the item frame creates a new map zoomed out to the maximum based on the current location. This did not happen with a few of the maps, as can be seen in the screenshots attached. These maps were created using an online map creator and skip several numbers and were placed in the newly added invisible item frames. The correct .dat files for the map are still in the game folder.
Reloading the 20w21a save back in 20w20b causes the game to freeze (however, the 20w21a world without the maps in the item frames can be seen briefly)
How to reproduce
- Have a world with maps in item frames
- Update it to 20w21a
- Try to use commands to give the filled map, e.g. /give @a minecraft:filled_map{map:103}
Logs
The logs have many entries like the following that seem to be related to the problem
[01:55:56] [Server thread/ERROR]: Not a string
[01:55:56] [Server thread/ERROR]: Error loading saved data: map_310011
java.lang.IllegalArgumentException: Invalid map dimension: 0b
at cyt.c(SourceFile:126) ~[20w21a.jar:?]
at cyt$$Lambda$4189/1620636011.get(Unknown Source) ~[?:?]
at java.util.Optional.orElseThrow(Optional.java:290) ~[?:1.8.0_51]
at cyt.a(SourceFile:126) ~[20w21a.jar:?]
at cyy.c(SourceFile:72) [20w21a.jar:?]
at cyy.b(SourceFile:58) [20w21a.jar:?]
at yw.a(SourceFile:1159) [20w21a.jar:?]
at bjt.a(SourceFile:59) [20w21a.jar:?]
at bjt.b(SourceFile:64) [20w21a.jar:?]
at yv.a(SourceFile:94) [20w21a.jar:?]
at yi.g(SourceFile:1070) [20w21a.jar:?]
at yu.p(SourceFile:398) [20w21a.jar:?]
at yu.a(SourceFile:337) [20w21a.jar:?]
at yw.a(SourceFile:347) [20w21a.jar:?]
at net.minecraft.server.MinecraftServer.b(SourceFile:893) [20w21a.jar:?]
at net.minecraft.server.MinecraftServer.a(SourceFile:832) [20w21a.jar:?]
at enr.a(SourceFile:89) [20w21a.jar:?]
at net.minecraft.server.MinecraftServer.run(SourceFile:691) [20w21a.jar:?]
at java.lang.Thread.run(Thread.java:745) [?:1.8.0_51]
Please read this in full before marking it as a duplicate of
MC-149835as it is not the same.In 1.14 to 1.14.3, if a villager is taken far away enough from their job block, they will immediately lose their job (not even having enough time to take them out of the boat). In 1.14.4 and 1.15.2, this change took 2 in-game hours in my testing. In 1.16.5, this change took an entire in-game day. In 1.17.1, this change did not happen within 7 in-game days. This occurs both on single player and multi player worlds hosted by other people.
This makes adventure-only challenge games much more difficult.
What I expected to happen was...:
Like in 1.14 to 1.14.3, villagers immediately lose their job if they are too far away and thus cannot pathfind to their job block. At the very least, like in 1.14.4 to 1.16.5, they will eventually lose their job after a while.What actually happened was...:
The villager did not seem to lose their job at all and would continuously try to walk back to their job block during job hours.Steps to Reproduce:
1. Create a world. Any world will work, but a superflat world with a blue ice floor will make it easier.
2. Spawn a villager and let them claim a job block.
3. Take them far away from their job block. In my testing, I used a boat to bring them 500 blocks away. Also be sure the time of day is between 2000 and 9000 so that the villager will attempt to change jobs. In my testing, I set the time to 3000.4. The villager will not lose their job seemingly no matter how long you wait.
Please read this in full before marking it as a duplicate of
MC-149835as it is not the same.In 1.14 to 1.14.3, if a villager is taken far away enough from their job block, they will immediately lose their job (not even having enough time to take them out of the boat). In 1.14.4 and 1.15.2, this change took 2 in-game hours in my testing. In 1.16.5, this change took an entire in-game day. In 1.17.1, this change did not happen within 7 in-game days. This occurs both on single player and multi player worlds hosted by other people and giving them a bed or other job blocks does not seem to change their behavior.
This makes adventure-only challenge games much more difficult.
What I expected to happen was...:
Like in 1.14 to 1.14.3, villagers immediately lose their job if they are too far away and thus cannot pathfind to their job block. At the very least, like in 1.14.4 to 1.16.5, they will eventually lose their job after a while.What actually happened was...:
The villager did not seem to lose their job at all and would continuously try to walk back to their job block during job hours.Steps to Reproduce:
1. Create a world. Any world will work, but a superflat world with a blue ice floor will make it easier.
2. Spawn a villager and let them claim a job block.
3. Take them far away from their job block. In my testing, I used a boat to bring them 500 blocks away. Also be sure the time of day is between 2000 and 9000 so that the villager will attempt to change jobs. In my testing, I set the time to 3000.4. The villager will not lose their job seemingly no matter how long you wait.
Please read this in full before marking it as a duplicate of
MC-149835as it is not the same.In 1.14 to 1.14.3, if a villager is taken far away enough from their job block, they will immediately lose their job (not even having enough time to take them out of the boat). In 1.14.4 and 1.15.2, this change took 2 in-game hours in my testing. In 1.16.5, this change took an entire in-game day. In 1.17.1, this change did not happen within 7 in-game days. This occurs both on single player and multi player worlds hosted by other people
and giving them a bed or other job blocks does not seem to change their behavior.This makes adventure-only challenge games much more difficult.
What I expected to happen was...:
Like in 1.14 to 1.14.3, villagers immediately lose their job if they are too far away and thus cannot pathfind to their job block. At the very least, like in 1.14.4 to 1.16.5, they will eventually lose their job after a while.What actually happened was...:
The villager did not seem to lose their job at all and would continuously try to walk back to their job block during job hours.Steps to Reproduce:
1. Create a world. Any world will work, but a superflat world with a blue ice floor will make it easier.
2. Spawn a villager and let them claim a job block.
3. Take them far away from their job block. In my testing, I used a boat to bring them 500 blocks away. Also be sure the time of day is between 2000 and 9000 so that the villager will attempt to change jobs. In my testing, I set the time to 3000.4. The villager will not lose their job seemingly no matter how long you wait.
Please read this in full before marking it as a duplicate of
MC-149835as it is not the same.In 1.14 to 1.14.3, if a villager is taken far away enough from their job block, they will immediately lose their job (not even having enough time to take them out of the boat). In 1.14.4 and 1.15.2, this change took 2 in-game hours in my testing. In 1.16.5, this change took an entire in-game day. In 1.17.1, this change did not happen within 7 in-game days. This occurs both on single player and multi player worlds hosted by other people. Giving them a bed or other job blocks does not seem to change their behavior.
This makes adventure-only challenge games much more difficult.
What I expected to happen was...:
Like in 1.14 to 1.14.3, villagers immediately lose their job if they are too far away and thus cannot pathfind to their job block. At the very least, like in 1.14.4 to 1.16.5, they will eventually lose their job after a while.What actually happened was...:
The villager did not seem to lose their job at all and would continuously try to walk back to their job block during job hours.Steps to Reproduce:
1. Create a world. Any world will work, but a superflat world with a blue ice floor will make it easier.
2. Spawn a villager and let them claim a job block.
3. Take them far away from their job block. In my testing, I used a boat to bring them 500 blocks away. Also be sure the time of day is between 2000 and 9000 so that the villager will attempt to change jobs. In my testing, I set the time to 3000.4. The villager will not lose their job seemingly no matter how long you wait.
Please read this in full before marking it as a duplicate of
MC-149835as it is not the same.In 1.14 to 1.14.3, if a villager is taken far away enough from their job block, they will immediately lose their job (not even having enough time to take them out of the boat). In 1.14.4 and 1.15.2, this change took 2 in-game hours in my testing. In 1.16.5, this change took an entire in-game day. In 1.17.1, this change did not happen within 7 in-game days. This occurs both on single player and multi player worlds hosted by other people. Giving them a bed or other job blocks does not seem to change their behavior. The screenshots below show a screenshot of what time it was when the villager lost their job after being taken far away from their job block, except for the 1.17 screenshot, which shows the villager still not losing their job despite waiting from Day 0 to Day 7.
This makes adventure-only challenge games much more difficult.
What I expected to happen was...:
Like in 1.14 to 1.14.3, villagers immediately lose their job if they are too far away and thus cannot pathfind to their job block. At the very least, like in 1.14.4 to 1.16.5, they will eventually lose their job after a while.What actually happened was...:
The villager did not seem to lose their job at all and would continuously try to walk back to their job block during job hours.Steps to Reproduce:
1. Create a world. Any world will work, but a superflat world with a blue ice floor will make it easier.
2. Spawn a villager and let them claim a job block.
3. Take them far away from their job block. In my testing, I used a boat to bring them 500 blocks away. Also be sure the time of day is between 2000 and 9000 so that the villager will attempt to change jobs. In my testing, I set the time to 3000.4. The villager will not lose their job seemingly no matter how long you wait.
Please read this in full before marking it as a duplicate of
MC-149835as it is not the same.In 1.14 to 1.14.3, if a villager is taken far away enough from their job block, they will immediately lose their job (not even having enough time to take them out of the boat). In 1.14.4 and 1.15.2, this change took 2 in-game hours in my testing. In 1.16.5, this change took an entire in-game day. In 1.17.1, this change did not happen within 7 in-game days. This occurs both on single player and multi player worlds hosted by other people. Giving them a bed or other job blocks does not seem to change their behavior. The screenshots below show a screenshot of what time it was when the villager lost their job after being taken far away from their job block, except for the 1.17 screenshot, which shows the villager still not losing their job despite waiting from Day 0 to Day 7.
This makes adventure-only challenge games much more difficult.
What I expected to happen was...:
Like in 1.14 to 1.14.3, villagers immediately lose their job if they are too far away and thus cannot pathfind to their job block. At the very least, like in 1.14.4 to 1.16.5, they will eventually lose their job after a while.What actually happened was...:
The villager did not seem to lose their job at all and would continuously try to walk back to their job block during job hours.Steps to Reproduce:
1. Create a world. Any world will work, but a superflat world with a blue ice floor will make it easier.
2. Spawn a villager and let them claim a job block.
3. Take them far away from their job block. In my testing, I used a boat to bring them 500 blocks away. Also be sure the time of day is between 2000 and 9000 so that the villager will attempt to change jobs. In my testing, I set the time to 3000.4. The villager will not lose their job seemingly no matter how long you wait.
Please read this in full before marking it as a duplicate of
MC-149835as it is not the same.In 1.14 to 1.14.3, if a villager is taken far away enough from their job block, they will immediately lose their job (not even having enough time to take them out of the boat). In 1.14.4 and 1.15.2, this change took 2 in-game hours in my testing. In 1.16.5, this change took an entire in-game day. In 1.17.1, this change did not happen within 7 in-game days. This occurs both on single player and multi player worlds hosted by other people. Giving them a bed or other job blocks does not seem to change their behavior. The screenshots below show a screenshot of what time it was when the villager lost their job after being taken far away from their job block, except for the 1.17 screenshot, which shows the villager still not losing their job despite waiting from Day 0 to Day 7.
This can be very annoying when transporting villagers large distances only to find that they will not change their jobs and will continuously try to walk to their old job site.
What I expected to happen was...:
Like in 1.14 to 1.14.3, villagers immediately lose their job if they are too far away and thus cannot pathfind to their job block. At the very least, like in 1.14.4 to 1.16.5, they will eventually lose their job after a while.What actually happened was...:
The villager did not seem to lose their job at all and would continuously try to walk back to their job block during job hours.Steps to Reproduce:
1. Create a world. Any world will work, but a superflat world with a blue ice floor will make it easier.
2. Spawn a villager and let them claim a job block.
3. Take them far away from their job block. In my testing, I used a boat to bring them 500 blocks away. Also be sure the time of day is between 2000 and 9000 so that the villager will attempt to change jobs. In my testing, I set the time to 3000.4. The villager will not lose their job seemingly no matter how long you wait.
Please read this in full before marking it as a duplicate of
MC-149835as it is not the same.In 1.14 to 1.14.3, if a villager is taken far away enough from their job block, they will immediately lose their job (not even having enough time to take them out of the boat). In 1.14.4 and 1.15.2, this change took 2 in-game hours in my testing. In 1.16.5, this change took an entire in-game day. In 1.17.1, this change did not happen within 7 in-game days. This occurs both on single player and multi player worlds hosted by other people. Giving them a bed or other job blocks does not seem to change their behavior. The screenshots below show a screenshot of what time it was when the villager lost their job after being taken far away from their job block, except for the 1.17 screenshot, which shows the villager still not losing their job despite waiting from Day 0 to Day 7.
This can be very annoying when transporting villagers large distances only to find that they will not change their jobs and will continuously try to walk to their old job site.
What I expected to happen was...:
Like in 1.14 to 1.14.3, villagers immediately lose their job if they are too far away and thus cannot pathfind to their job block. At the very least, like in 1.14.4 to 1.16.5, they will eventually lose their job after a while.What actually happened was...:
The villager did not seem to lose their job at all and would continuously try to walk back to their job block during job hours.Steps to Reproduce:
1. Create a world. Any world will work, but a superflat world with a blue ice floor will make it easier.
2. Spawn a villager and let them claim a job block.
3. Take them far away from their job block. In my testing, I used a boat to bring them 500 blocks away. Also be sure the time of day is between 2000 and 9000 so that the villager will attempt to change jobs. In my testing, I set the time to 3000.4. The villager will not lose their job
seemingly no matter how long you wait.Please read this in full before marking it as a duplicate of
MC-149835as it is not the same.In 1.14 to 1.14.3, if a villager is taken far away enough from their job block, they will immediately lose their job (not even having enough time to take them out of the boat). In 1.14.4 and 1.15.2, this change took 2 in-game hours in my testing. In 1.16.5, this change took an entire in-game day. In 1.17.1, this change did not happen within 7 in-game days. This occurs both on single player and multi player worlds hosted by other people. Giving them a bed or other job blocks does not seem to change their behavior. The screenshots below show a screenshot of what time it was when the villager lost their job after being taken far away from their job block, except for the 1.17 screenshot, which shows the villager still not losing their job despite waiting from Day 0 to Day 7. The villager will eventually lose their job, which they did on a server I was on, but it takes an extremely long time (roughly 100 in-game days).
This can be very annoying when transporting villagers large distances only to find that they will not change their jobs and will continuously try to walk to their old job site.
What I expected to happen was...:
Like in 1.14 to 1.14.3, villagers immediately lose their job if they are too far away and thus cannot pathfind to their job block. At the very least, like in 1.14.4 to 1.16.5, they will eventually lose their job after a while.What actually happened was...:
The villager did not seem to lose their job at all and would continuously try to walk back to their job block during job hours.Steps to Reproduce:
1. Create a world. Any world will work, but a superflat world with a blue ice floor will make it easier.
2. Spawn a villager and let them claim a job block.
3. Take them far away from their job block. In my testing, I used a boat to bring them 500 blocks away. Also be sure the time of day is between 2000 and 9000 so that the villager will attempt to change jobs. In my testing, I set the time to 3000.4. The villager will not lose their job for a very long time.
Please read this in full before marking it as a duplicate of
MC-149835as it is not the same.In 1.14 to 1.14.3, if a villager is taken far away enough from their job block, they will immediately lose their job (not even having enough time to take them out of the boat). In 1.14.4 and 1.15.2, this change took 2 in-game hours in my testing. In 1.16.5, this change took an entire in-game day. In 1.17.1, this change did not happen within 7 in-game days. This occurs both on single player and multi player worlds hosted by other people. Giving them a bed or other job blocks does not seem to change their behavior. The screenshots below show a screenshot of what time it was when the villager lost their job after being taken far away from their job block, except for the 1.17 screenshot, which shows the villager still not losing their job despite waiting from Day 0 to Day 7. The villager will eventually lose their job, which they did on a server I was on, but it takes an extremely long time (roughly
100 in-game days).This can be very annoying when transporting villagers large distances only to find that they will not change their jobs and will continuously try to walk to their old job site.
What I expected to happen was...:
Like in 1.14 to 1.14.3, villagers immediately lose their job if they are too far away and thus cannot pathfind to their job block. At the very least, like in 1.14.4 to 1.16.5, they will eventually lose their job after a while.What actually happened was...:
The villager did not seem to lose their job at all and would continuously try to walk back to their job block during job hours.Steps to Reproduce:
1. Create a world. Any world will work, but a superflat world with a blue ice floor will make it easier.
2. Spawn a villager and let them claim a job block.
3. Take them far away from their job block. In my testing, I used a boat to bring them 500 blocks away. Also be sure the time of day is between 2000 and 9000 so that the villager will attempt to change jobs. In my testing, I set the time to 3000.4. The villager will not lose their job for a very long time.
Please read this in full before marking it as a duplicate of
MC-149835as it is not the same.In 1.14 to 1.14.3, if a villager is taken far away enough from their job block, they will immediately lose their job (not even having enough time to take them out of the boat). In 1.14.4 and 1.15.2, this change took 2 in-game hours in my testing. In 1.16.5, this change took an entire in-game day. In 1.17.1, this change did not happen within 7 in-game days. This occurs both on single player and multi player worlds hosted by other people. Giving them a bed or other job blocks does not seem to change their behavior. The screenshots below show a screenshot of what time it was when the villager lost their job after being taken far away from their job block, except for the 1.17 screenshot, which shows the villager still not losing their job despite waiting from Day 0 to Day 7. The villager will eventually lose their job, which they did on a server I was on, but it takes an extremely long time (roughly 50 in-game days, I do not have any exact measurements).
This can be very annoying when transporting villagers large distances only to find that they will not change their jobs and will continuously try to walk to their old job site.
What I expected to happen was...:
Like in 1.14 to 1.14.3, villagers immediately lose their job if they are too far away and thus cannot pathfind to their job block. At the very least, like in 1.14.4 to 1.16.5, they will eventually lose their job after a while.What actually happened was...:
The villager did not seem to lose their job at all and would continuously try to walk back to their job block during job hours.Steps to Reproduce:
1. Create a world. Any world will work, but a superflat world with a blue ice floor will make it easier.
2. Spawn a villager and let them claim a job block.
3. Take them far away from their job block. In my testing, I used a boat to bring them 500 blocks away. Also be sure the time of day is between 2000 and 9000 so that the villager will attempt to change jobs. In my testing, I set the time to 3000.4. The villager will not lose their job for a very long time.
Please read this in full before marking it as a duplicate of
MC-149835as it is not the same.In 1.14 to 1.14.3, if a villager is taken far away enough from their job block, they will immediately lose their job (not even having enough time to take them out of the boat that I used for testing). In 1.14.4 and 1.15.2, this change took 2 in-game hours in my testing. In 1.16.5, this change took an entire in-game day. In 1.17.1, this change did not happen within 7 in-game days. This occurs both on single player and multi player worlds hosted by other people. Giving them a bed or other job blocks does not seem to change their behavior. The screenshots below show a screenshot of what time it was when the villager lost their job after being taken far away from their job block, except for the 1.17 screenshot, which shows the villager still not losing their job despite waiting from Day 0 to Day 7. The villager will eventually lose their job, which they did on a server I was on, but it takes an extremely long time (roughly 50 in-game days, I do not have any exact measurements).
This can be very annoying when transporting villagers large distances only to find that they will not change their jobs and will continuously try to walk to their old job site.
What I expected to happen was...:
Like in 1.14 to 1.14.3, villagers immediately lose their job if they are too far away and thus cannot pathfind to their job block. At the very least, like in 1.14.4 to 1.16.5, they will eventually lose their job after a while.What actually happened was...:
The villager did not seem to lose their job at all and would continuously try to walk back to their job block during job hours.Steps to Reproduce:
1. Create a world. Any world will work, but a superflat world with a blue ice floor will make it easier.
2. Spawn a villager and let them claim a job block.
3. Take them far away from their job block. In my testing, I used a boat to bring them 500 blocks away. Also be sure the time of day is between 2000 and 9000 so that the villager will attempt to change jobs. In my testing, I set the time to 3000.4. The villager will not lose their job for a very long time.
Please read this in full before marking it as a duplicate of
MC-149835as it is not the same.In 1.14 to 1.14.3, if a villager is taken far away enough from their job block, they will immediately lose their job (not even having enough time to take them out of the boat that I used for testing). In 1.14.4 and 1.15.2, this change took 2 in-game hours in my testing. In 1.16.5, this change took an entire in-game day. In 1.17.1, this change did not happen within 7 in-game days. This occurs both on single player and multi player worlds hosted by other people. Giving them a bed or other job blocks does not seem to change their behavior. The screenshots below show a screenshot of what time it was when the villager lost their job after being taken far away from their job block, except for the 1.17 screenshot, which shows the villager still not losing their job despite waiting from Day 0 to Day 7. The villager will eventually lose their job, which they did on a server I was on, but it takes an extremely long time (roughly 50 in-game days, I do not have any exact measurements).
This can be very annoying when transporting villagers large distances only to find that they will not change their jobs and will continuously try to walk to their old job site.
What I expected to happen was...:
Like in 1.14 to 1.14.3, villagers immediately lose their job if they are too far away and thus cannot pathfind to their job block. At the very least, like in 1.14.4 to 1.16.5, they will eventually lose their job after a while.What actually happened was...:
The villager did not seem to lose their job at all and would continuously try to walk back to their job block during job hours.Steps to Reproduce:
1. Create a world. Any world will work, but a superflat world with a blue ice floor will make it easier.
2. Spawn a villager and let them claim a job block.
3. Take them far away from their job block. In my testing, I used a boat to bring them 500 blocks away. Also be sure the time of day is between 2000 and 9000 so that the villager will attempt to change jobs. In my testing, I set the time to 3000.4. The villager will not lose their job for a very long time.
Please read this in full before marking it as a duplicate of
MC-149835as it is not the same.In 1.14 to 1.14.3, if a villager is taken far away enough from their job block, they will immediately lose their job (not even having enough time to take them out of the boat that I used for testing). In 1.14.4 and 1.15.2, this change took 2 in-game hours in my testing. In 1.16.5, this change took an entire in-game day. In 1.17.1, this change did not happen within 7 in-game days. This occurs both on single player and multi player worlds hosted by other people. Giving them a bed or other job blocks does not seem to change their behavior. The screenshots below show a screenshot of what time it was when the villager lost their job after being taken far away from their job block, except for the 1.17 screenshot, which shows the villager still not losing their job despite waiting from Day 0 to Day 7. The villager will eventually lose their job, which they did on a server I was on, but it takes an extremely long time (roughly 50 in-game days, I do not have any exact measurements).
This can be very annoying when transporting villagers large distances only to find that they will not change their jobs and will continuously try to walk to their old job site.
What I expected to happen was...:
Like in 1.14 to 1.14.3, villagers immediately lose their job if they are too far away and thus cannot pathfind to their job block. At the very least, like in 1.14.4 to 1.16.5, they will eventually lose their job after a while.What actually happened was...:
The villager did not seem to lose their job at all and would continuously try to walk back to their job block during job hours.Steps to Reproduce:
1. Create a world. Any world will work, but a superflat world with a blue ice floor will make it easier.
2. Spawn a villager and let them claim a job block.
3. Take them far away from their job block. In my testing, I used a boat to bring them 500 blocks away. Also be sure the time of day is between 2000 and 9000 so that the villager will attempt to change jobs. In my testing, I set the time to 3000.4. The villager will not lose their job for a very long time.
Please read this in full before marking it as a duplicate of
MC-149835as it is not the same.In 1.14 to 1.14.3, if a villager is taken far away enough from their job block, they will immediately lose their job (not even having enough time to take them out of the boat that I used for testing). In 1.14.4 and 1.15.2, this change took 2 in-game hours in my testing. In 1.16.5, this change took an entire in-game day. In 1.17.1, this change did not happen within 7 in-game days. This occurs both on single player and multi player worlds hosted by other people. Giving them a bed or other job blocks does not seem to change their behavior. The screenshots below show a screenshot of what time it was when the villager lost their job after being taken far away from their job block, except for the 1.17 screenshot, which shows the villager still not losing their job despite waiting from Day 0 to Day 7. The villager will eventually lose their job, which they did on a server I was on, but it takes an extremely long time (roughly 50 in-game days, I do not have any exact measurements).
This can be very annoying when transporting villagers large distances only to find that they will not change their jobs and will continuously try to walk to their old job site.
What I expected to happen was...:
Like in versions 1.14 to 1.14.3, villagers immediately lose their job if they are too far away and thus cannot pathfind to their job block. At the very least, like in 1.14.4 to 1.16.5, they will eventually lose their job after a while.What actually happened was...:
The villager did not seem to lose their job at all and would continuously try to walk back to their job block during job hours.Steps to Reproduce:
1. Create a world. Any world will work, but a superflat world with a blue ice floor will make it easier.
2. Spawn a villager and let them claim a job block.
3. Take them far away from their job block. In my testing, I used a boat to bring them 500 blocks away. Also be sure the time of day is between 2000 and 9000 so that the villager will attempt to change jobs. In my testing, I set the time to 3000.4. The villager will not lose their job for a very long time.
Please read this in full before marking it as a duplicate of
MC-149835as it is not the same.In 1.14 to 1.14.3, if a villager is taken far away enough from their job block, they will immediately lose their job (not even having enough time to take them out of the boat that I used for testing). In 1.14.4 and 1.15.2, this change took 2 in-game hours in my testing. In 1.16.5, this change took an entire in-game day. In 1.17.1, this change did not happen within 7 in-game days. This occurs both on single player and multi player worlds hosted by other people. Giving them a bed or other job blocks does not seem to change their behavior. The screenshots below show a screenshot of what time it was when the villager lost their job after being taken far away from their job block, except for the 1.17 screenshot, which shows the villager still not losing their job despite waiting from Day 0 to Day 7. The villager will eventually lose their job, which they did on a server I was on, but it takes an extremely long time (roughly 50 in-game days, I do not have any exact measurements).
This can be very annoying when transporting villagers large distances only to find that they will not change their jobs and will continuously try to walk to their old job site.
What I expected to happen was...:
Like in versions 1.14 to 1.14.3, villagers immediately lose their job if they are too far away and thus cannot pathfind to their job block. At the very least, like in versions 1.14.4 to 1.16.5, they will eventually lose their job after a while.What actually happened was...:
The villager did not seem to lose their job at all and would continuously try to walk back to their job block during job hours.Steps to Reproduce:
1. Create a world. Any world will work, but a superflat world with a blue ice floor will make it easier.
2. Spawn a villager and let them claim a job block.
3. Take them far away from their job block. In my testing, I used a boat to bring them 500 blocks away. Also be sure the time of day is between 2000 and 9000 so that the villager will attempt to change jobs. In my testing, I set the time to 3000.4. The villager will not lose their job for a very long time.
I created this world in a 1.16 snapshot version, so these maps do not use the pre-18w31a map format.
I wonder why some of the maps stayed intact - did any of the maps stay intact while you were testing?