Markus Haberstock
- wolfeye
- wolfeye
- Europe/Stockholm
- Yes
- No
MC-30527![[Mojang] Nathan Adams](../../../data/assets/gravatar/dinnerbone.png){kind=small}
Achievement "Adventuring Time" doesn't work.
I visited all biomes including the variants and the achievement was not unlocked.
I suspect it is because the biomes 10 "Frozen Ocean" and 20 "Extreme Hills Edge" don't generate in this snapshot.Steps to Reproduce:
1. Visit all biomes and variants (there are two different "Mega Spruce Taiga"
2. You will not get the achievementEdit: It only works if the ONLY biomes visited are the existing non-variant biomes except Nether and End.
Achievement "Adventuring Time" does not work right
@Markus Haberstock: That is a separate bug, MC-31006. Even when the game is left open from beginning to end (and thus, MC-31006 does not apply), this bug still applies.
Andrés del Campo Novales: The latest snapshot is the version we're supposed to be testing bugs in, so I'm assuming Markus Haberstock is referring to 14w11b.
@Markus Haberstock: Does this issue persist for you?
I did not miss a biome. I even used MCEdit to cheat and get Frozen Ocean and Extreme Hills Edge. And I didn't miss any of the rare variants (Ms and others - checked the wiki). I checked twice. I even checked my .json file.
no change in 13w39a.
Works now strangely enough. Can't reproduce.
It was raining in that world when I changed to the newest snapshot.
The rain animation didn't stop.
The rain was gone after closing minecraft and starting it again.
Now it works.
Now it's worse. 13w42b - The progress made in biomes is reset every time I leave minecraft and restart the launcher. more precise: the json file looses all biome progress on restart.
Still occurs in 1.7 Prerelease.
Still occurs in 1.7 Prerelease and in 1.7.1
confirmed for 1.7.1
Does this work? I still can't get it.
It's not resolved. Please reopen!
This works now but
MC-30527still doesn'tOh, it does record all biomes in the json file, it just doesn't complete the achievement even if all existing biomes (and two non-existing ones) are recorded.
It may be because there are two biomes named the same: "Mega Spruce Taiga" (biomes 160 and 161).
#Daniel Simmons: Nice!
I tried your idea to only visit all biomes < 128, but it didn't work.
I used a world where I edited in the two missing biomes, then I also edited my json-file, but still.
Success!
(Sort of)
I cleared my list of visited biomes in the .json file and visited ONLY the list of biomes above (i.e. excluding 8 Hell (The Nether), 9 Sky (The End), 10 FrozenOcean, 20 Extreme Hills Edge, also excluding all variants) and I got the achievement.
Including even one of the other biomes prohibits you from getting the achievement.
And that's the problem. In Survival you can't get to the achievement without visiting Nether and End, also you will not be able to miss all variant biomes and sometimes you even visit only a variant, because it is almost indistinguisheable from a non-variant: e.g. Swampland and Swampland M.
To work right, this achievement should check if you visited a biome or its variant (or both) and ignore all visits to Nether and End.
It's the latest snapshot 14w11b I was using. I did try the same in earlier snapshots (with and without 10/20 or 8/9), but this is the first time where it worked. It's quite possible that I goofed at my earlier attempts.
JungleEdge does generate, albeit very rarely. It's always near Jungle M, but appears only rarely even there.
Still happens on 14w31a. It's not very strong, but it just happened to me.
It is fixed. You have to visit all the non-variant biomes though. I don't think the variants are registering as the proper biomes.
Confirm. Also the minutes shown are not consecutive, even if they should be.
It seems to be fixed since January, 25th
The problem of not being able to transport a horse in a boat could be solved by making it so that the Frostwalker enchantment works when riding a horse, in that way you could ride atop a frosted ocean with your horse.
Still a problem in 1.14.1 full release.
It was fixed in 1.14.2 Pre-Release 1. It's again broken in Pre-Release 2
The problem persists in 1.14.2. Pre-Release 3
Still in 1.14.2 Pre-Release 4
Not fixed in the full release 1.14.2
I'm not sure, but it seems to be fixed in 1.14.3 Pre-Release 1
I just encountered this some days ago in 1.14.4.
Checking the newest snapshot, it still persists: 19w40a
It's not exactly 'hard' power it's reacting to. If you power a block with a comparator it's also 'hard' powered. It is strongly powered with the signal strength you put into the comparator. The calibrated sculk sensor doesn't react to that signal strength and it should.
This may be intended, but something made of wood not dropping anything when you use a diamond axe on it is not very intuitive