Adventure Mode breaking transparent blocks

Agreed with Gerrard. Perhaps a method to add blocks to a whitelist via an NBT editor. The blocks added would be those that can be broken; so by default, if nothing is added to the whitelist, no blocks can be broken whatsoever (though this may clash with the "right tool for the right block" bit; perhaps that could be a gamerule instead?).

nope, that's not going to happen Gerrard Lukacs and Skylinerw, that would be a whole new feature. For now the only thing you can expect to happen is that it will not be breakable.
But I agree that that would be nice.

DEFINITELY needs to be fixed, this is really annoying because now all server owners and map makers for multiplayer servers need to hide glowstone and so on behind glass so adventure mode users can't break it.

EDIT: Just realised that glass is also breakable...

I don't quite understand why this isn't fixed yet, since this is one of the most game breaking bugs in minecraft.
I'm not sure why this bug only has 12 votes either.

Mojang added a feature on adventure mode that some tools can break some tipes of blocks , try to use a pickaxe on adventure mode, and you'll be able to break stone and ores, the fists have their own blocks as well, i don't think that's a bug, it's totally intended.

Although i can be wrong, I think i'm right, because i read the version updates logs and the adventure mode has it's own properties depending on the tools you use to break blocks since... 1.4.2 i think, or 1.4.4

Well... That sucks then... And I think I'm not the only one who thinks this.

Whether the breaking of glowstone, beacons, etc. by hand was intentional, it is still a game-breaking change. If the redstone update makes it impossible to construct even the most basic logic gates, whether or not the changes therein may be intended, the consequences are not necessarily intentional. Thus, this report is still valid, as far as I can see.

Also, breaking stuff by hand in adventure mode was not possible back when breaking things via tools was first released. This seems to be a side-effect of attempting to let players break glass in adventure mode.

EDIT: By the way, Skylinerw, item frames and paintings are entities, not blocks. They could be broken prior to this update as well. Fortunately, as entities, you can give them the Invulnerable property via an NBT editor (I was actually working on an MCedit filter to help streamline this and remove the need for NBT editing), and players will not be able to break them. However, they will still be able to break blocks behind them, causing them to drop.

@Gerrad Mm, I included the item frames and paintings due to a biased opinion that they shouldn't be broken with fists 😉. Wasn't aware about making them invulnerable though, thanks for that!

I've got an idea which you might want to use untill this (maybe) bug is fixed. Not sure if it's used already but I wanted to share it with you guys.
Make a spawner spawning thrown potions of mining fatigue. With level trazillion. Then set everybody's spawnpoint there and make them tp back to their intended spawnpoint using a pressure plate. Then they can't break anything unless they want to wait a trazillion days.

I tested it and it works, but it has a lot of downsides. Read below.

That has the downside of making players's attack animations ridiculously slow, and also, what if you want the player to be able to sleep in beds to set spawn?

Also, you can't let your player obtain milk in the map (which means either no hostile mob spawning, so they can't get iron for a bucket, or no passive mob spawning, so they can't get a cow/mooshroom). Milk would cure them of the mining fatigue status, however long its duration.

The pressure plate teleport idea doesn't work for me because there's also a bug causing redstone to stay activated if you teleport too far so the chunks will unload 😞

Vote for it here: https://mojang.atlassian.net/browse/MC-711

there are a lot of downsides on the mining fatigue potion idea, but it works. And we have to do it with this for now. I still think this is a bug and should be fixed of course. And by the way, beds still work with this potion. Basically all the right clicking actions work. And for the milk, you would have to prevent cows for spawning.

If a player sleeps in a bed, their spawn will no longer be the potioning area. Then they can just suicide and cheat on their merry way.

Don't make beds.

Ain't it lovely?

• No beds

• No cows

• No zombies or no water (iron = bucket = wall-climbing with water. Also, solidifying lava)

• No witches or other sources of sticks (sticks = ladders, again wall-climbing)

• No source of sand/gunpowder (TNT still blows up map, regardless of any gameRules)

I think I'd rather just have back the version of Adventure Mode that didn't let players place/remove blocks. As a new gamemode, I suppose, because the new Adventure Mode has its own uses. These 'workarounds' are hardly preferable.

Yup, I agree with you. There SHOULD be a way to set all the staf you do/don't want to be possible in the map. But if you want that, I think you ask way to much from the mojangsters to program.

Eh, all I'm asking for is to have back what we once had. The original adventure mode existed as it was up until the Pretty Scary Update, which gave plenty of time for plenty of map-makers to rely on its ability to prevent cheating. Then, it was basically removed and replaced with 'you can place anything, and remove anything you have the tool for'. The ability to break transparent blocks by hand is another nail in the coffin for the anti-cheat use of Adventure Mode, but that purpose was already pretty much ruined at the dawn of 1.4.

While it would be an amazing thing if Mojang could make all map makers happy, able to fine-tune whatever the player can/can't do, I'll have to agree with you that it would be too much effort, considering their current focus is the redstone update and preparations for the API. Having an NBT whitelist/blacklist of blocks which can be placed/removed in Adventure Mode may be more manageable and easier to implement, but again, I don't see Mojang taking that much time away from the next major update.

Still, I'll have to agree with Sethbling and suggest, "gamemode 3 please?" 😛

I agree

Before a mod asks for it, yes this still happens in 1.4.6

this is a duplicate of MC-2367 btw

This isn't a duplicate, it's a related report. Breaking transparent blocks started in 1.4.4, while the other report's issue started in 1.4.2 (and actually dates back to snapshots from a month earlier than that). It's possible some people want an adventure mode where tools can be used to break blocks, but your hands can't (I don't personally fall in that category, however - I'd rather see both issues eventually be addressed).

confirmed for 13w03a

Confirmed for 13w04a

I have experienced this in 1.4.7 when in adventure mode and I tried to break tripwires. On a server.

Confirmed for 13w05b.

The ability to break ladders, rails, levers, beacons, buttons is an issue in adventure mode.

confirmed for 13w09c

Also happens with comparators in 1.5.

I think this is related to MC-2367

that's actually a useful feature , if fixed you're break alot of custom maps such as hypixel's herobrine's return

And yet, adding this feature broke a lot of custom maps such as Hypixel & SethBling's Team Fortress 2 map. Its preceding feature, the ability to place and break blocks in Adventure at all, broke thousands of more maps.

They really should add new gamemodes with the old behaviors, so these maps can be fixed, or add a gamerule to determine the behavior of Adventure mode.

New versions of Minecraft had always been backward-incompatible. An example is the 1.5 Redstone Update, which changed the redstone behaviour.

Adventure mode should not allow breaking blocks at all. If a custom map needs to allow players to break blocks, it can give the players the appropriate tools instead, and this should always work.

Personally, I can see both points of view, Yes breaking glass is useful for some adventure maps, but it also can be used to easily cheat as there is no transparent block that can not be broken. I do have a solution. Simply add a gamerule to disable breaking blocks completely. Only interacting with blocks like levers and chests. That will help a lot of people and help map makers a TON. Please consider this.

@Dakotah Yeah, we've all said that a trazillion times, but I guess they want to implement that when no one plays minecraft anymore.

It should be noted that these new items can be broken with bare fists in 1.6.1:

Wool Carpets
Comparators

Still not seeing why.

I'm pretty sure this is intended. It's got 68 votes. I don't think mojang hasn't seen anything of this bug yet.

Why isn't this fixed yet? This is like a TOP PRIORITY bug?

Alijah: Because;
1) It isn't a bug, it's an intended feature.
2) As a feature, it has been repeatedly discussed on the forums in great, heated detail.
3) In the discussions, the main arguments that this feature breaks certain things in many adventure maps falls apart after some thought on it. For example, concerning beds; "spiders drop string, which can be crafted into wool and then into beds". Well, where did the 7 wood planks to make a crafting table and a bed magically come from? With tile drops off, they're literally impossible to get legitimately. And so on and so forth.

So, overall, not a bug, and suggestions for new features belong on the forums.

For all those who wish to find out the logic used on both sides of the argument, please look over this thread, it's a good example..

Neospector:

/gamerule doAdventureCanBreakBlocks true/false

DONE. Issue closed forever.

Neospector:
You don't need to turn wool into a bed to abuse it. One wool block can be adequate to skip a large portion of a map, among other things (Herobrine's Return is one popular map where this would be possible, save for the lack of spiders - if you could obtain any placeable block, you could skip Dina Bone's mansion and battle, for example).

Yes, you have provided workarounds for nearly every reason people have said this bug/feature/behavior is a problem. Now, can we sit back and look at the implications these workarounds have for a cheat-free map?

• Look at the third post in this thread. That is the list of blocks you cannot use, except in situations where you don't mind players breaking them.

• The implication of that list is that if you don't want players to be able to destroy lighting (and they do do this in PvP and server maps, surprisingly often, intentionally or not), you must either have it out of reach (which also reduces the effectiveness of light, as the most potent light sources die out over just 15 blocks), or use non-torch/glowstone/lamp/beacon lighting.

• This latter choice leaves you with more unusual lighting choices, such as jack o' lanterns and active furnaces, and the risky choice of fire/lava. For fire/lava, if you don't want them to be dangerous, you need to place them in a way that players cannot come into contact with them and such that griefers cannot release them via breaking transparent blocks.

• The lack of redstone lamps as an effective choice means you need to use more complicated mechanisms, such as piston systems or lava dispensers, even when redstone lamps would be preferable.

• Perhaps more disturbingly, levers, buttons, and tripwire are also on that list. One player decided to use pressure plates everywhere instead, and you hand-waved this as a "choice". The alternative is that a player on a server could full well decide to grief levers/buttons, rendering the map unplayable without an admin's help, and a cheater in single/multiplayer could take those buttons/levers and place them elsewhere to activate redstone and cheat past harder parts of the map.

• Ladders and vines should be avoided, as they also offer griefers and cheaters some powerful opportunities. Sans shears, breaking vines won't get you anything but grief, but ladders can be broken after you no longer need them, and used to cheat at parkour or skip entire areas.

• If you have spiders, the string drop is more than common enough and the recipe for wool does not require any crafting table.

• Similarly, sheep drop wool directly, and snow golems drop snowballs which can be turned into blocks sans crafting table. A less common issue is glowstone dust dropped by witches.

• If crafting tables are made available to the player, even more possibilities are opened - gold from pigmen and iron from zombies, for example, also can make blocks. More importantly, sticks can be obtained from witches, making tools craftable. Iron's status as a rare drop doesn't make it negligible; I've been saved by earning iron purely from zombies before.

• Natural hostile mob spawning of any sort, apart from the End/Nether biome, means the possibility of encountering a zombie which drops an iron shovel. A small chance, but that doesn't mean it hasn't happened to me in adventure maps. The alternative is that the mapmaker must turn mob spawning off, and if they desire hostiles, spawners or persistent mobs are required as a workaround.

• The issues caused by tools and placeable blocks can be worked around by using a clock running the /clear command. This, of course, bans the existence of these items in the map, and also can induce lag when you consider just how large the list of banned items is and how many command blocks it requires.

• The alternative, of course, is to ban the source of these items - viz. spiders, sheep, snow golems, and witches. In a map where crafting tables are available, you must also ban zombies, zombie pigmen, and iron golems.

The list goes on and on. Principally, you can make a workaround for anything. Even if Mojang made adventure mode identical to survival, you can make the exposed region of your map entirely out of blocks such as bedrock, commandblocks, and end portal frames without fear of grief or cheaters.

But it should be fairly obvious that every workaround has its consequences. You seem to be entirely fine with removing the crafting table mechanic from adventure maps - but that doesn't mean that other map makers don't want this age-old mechanic to be available in their maps. Similarly, as glowstone can be abused, yet remains an integral component in the brewing system, map makers must make a choice: ban glowstone and prevent cheating, at the cost of nerfing brewing? Nevermind the people who use glass or glowstone in their builds, and the people who use redstone lamps, buttons, and levers to let their players interface with redstone mechanisms.

I, for one, am sick of the idea of throwing away dozens of perfectly good mechanics, mobs, items, and blocks, simply because of a series of changes that broke one mechanic. I am continuing my mapmaking as I would have if Adventure Mode was never created - with a simple sign at the start saying "placing and breaking blocks is against the rules, except in situations where the map tells you to." For multiplayer, where maps like this get griefed to the core even with a small playerbase (typically non-constructive griefing which renders the map unplayable, rather than coherent cheating), I'm relying on WorldGuard and Bukkit for anti-cheat.

But just because I've found yet another workaround - one that works for me - doesn't mean this is a non-issue. Whether or not Mojang intended all of these blocks to be hand-broken in adventure mode, I doubt they intended to break as many maps as they did. I've spoken with Hypixel, and he's said that it's a major nuisance to try working around the adventure mode changes. Whether or not he has successfully done so in his maps, just as everybody has been adjusting their maps to work in the new system, it remains a fact that the original adventure mode offered possibilities which the current one does not, and many maps and concepts were broken by this series of changes.

Yes, the new adventure mode has made things possible too - you've made this clear. Essentially, however, the old adventure mode and new adventure mode are features of a different nature. One feature was removed, and another was added in its place. In the process, many existing maps and servers were broken. Unless Mojang comes here and says that they intended to break these maps and servers, this is not "Works as Intended", regardless of whether the base behavior is intended.

OK I don't care anymore, but then just throw away adventure mode, it's useless this way.

Gerrad: Regardless of how silly you may believe it to be, it is indeed "Works as Intended", as stated in the changelogs for 1.4.2. This is not the place to be arguing why or why it should not be changed, and you should take it up on the forums.
Alijah: That is what I posted on the thread as what I would preferred, yes. Again, on the forums.

The wiki only documents observed behavior - it makes no statement on whether this behavior (or its consequences) are intended, save for when a statement by a Mojang employee is provided.

I don't think breaking beacons (and various other blocks on that list) by fist are intended, and I certainly don't think the damage dealt to maps and servers by the changes is intended, and as of yet, Mojang has not made any conclusive statements on the matter. Intention can't be guaged by observation of the game's behavior or words on a wiki - it comes from statements by Mojang, and we're currently lacking in those.

This is the place to be discussing whether this ticket should be closed as "Works as Intended" or left as "Unresolved". My post highlights the fact that, in order to repair maps and servers from before this change, an elaborate series of workarounds are needed, which have map-breaking side-effects of their own. I don't see how Mojang would intend its users to do all this, hence I am making my argument that the consequences of these changes were not intended. This would not be the first time the JIRA has handled tickets for an intended change with unintended consequences - see MC-973, for example. But, as I said, we should seek comment from Mojang on the matter.

Then you should still take it up on the forums.
If not because of whether the feature in question was intended or not, then because of the organization of the website; this site isn't built to handle long discussions of merits of opposing views. The forums and Reddit are.

Oh, and this issue isn't an opinion? https://mojang.atlassian.net/browse/MC-16222

"This is a new map made by hypixel! Let's see the lobby. Oh look there's a glowstone! Oh wait we can break the glowstone because in adventure mode you can break transparent block! *breaks *
Glampkoo fell out of the world."

@Alijah Yes it is.

That issue is not an opinion. It was an accidental change, whereas this is simply what adventure mode is.

discussing isn't going to change anything, just resolve it as 'works as intended' or fix it. But discussing until no one plays minecraft anymore isn't going to help.

70 votes. No, no, not work as intended. Or they will disappoint a lot of people.

Daniel: Works as intended does not mean it cannot be changed, it means you need to take it up with the developers elsewhere to get it changed. That is all.

http://www.youtube.com/watch?v=EWyo_S1jut8 In the meantime, someone's come up with a very complicated workaround to this awful bug.

yeah, I had the same idea but it gives you a shadow, and it causes a lot of lag, and it is a lot of work.

Can Mod please update affected Versions to 1.6 / 1.6.1 / 1.6.2 ? Thank you 🙂

Seems kind of odd. Even if you was intended, they would've changed it by now due to the shear number of votes, or else, closed the issue.