NickNackGus
Assigned
Reported
MCL-17255
.minecraft can no longer be a symlink
Fixed
MC-151339
Data packs load extension-only files
Confirmed
MC-146366
Written book titles don't use raw json text
Cannot Reproduce
MC-125292
Invalid syntax in datapack tag files crash Minecraft
Awaiting Response
MC-125166
"/bossbar set players" does not allow removing players from the bossbar
Invalid
MC-124301
Vines break if placed beneath a block they cannot connect to
Duplicate
MC-120507
Item duplication via /give
Confirmed
MC-118354
Advancement backgrounds repeat incorrectly for non-square images
Confirmed
MC-34675
Maps remain loaded across worlds/saves
Fixed
MC-34263
Ravine half filled by overlapping river biome
Works As Intended
Comments
That sounds like it should be a new bug report, assuming other particles aren't causing issues.
It isn't a problem for normal worlds, but it is a problem for mapmakers using /give.
This bug still exists. Aside from some stone being replaced by the new stone variants, the screenshot could be reproduced exactly in 14w30c. I wonder if this bug is because ravines aren't allowed in river biomes, in which case enabling them would be no different than having ravines in ocean biomes.
Actually, this bug was fixed exactly on the official release of 1.7.2. I just haven't found a button to close the report.
Not a duplicate of MC-33193. This is about map data of the same ID being shared across save files, not map locations being shared across dimensions or worlds. The screenshots I've attached show the effects of opening one save after another, and the map data being left in cache. The contents of the map appear in the other save, misrepresenting terrain and images contained in maps.
Although I do not know any 1.7 servers to test this with, in theory loading a map in single player and going onto a 1.7 server would make it appear as though your single player maps were on the server, and vice versa.
As for Meta's comment, deleting the map data files does NOT fix this bug, but restarting Minecraft does. I agree that it sounds like a feature, saving time in loading maps. However, it sounds like that feature was poorly implemented.
Bug still exists in 1.7.1, updated version information.
Keep in mind this issue will affect all worlds in all affected versions. I'm not sure if current/previous versions will be playable after January 19, 2038. It should be possible to test by changing your system clock, however.