PSA: Regarding certain item ids during the 1.6-1.7 transition

[IQD]

A few users decided to get some kicks out of telling other people to give themselves a few technical items on BuildBox. Those people's clients crashed and they are now unable to get online until their inventory is wiped. The offenders have been banned.

Anybody telling users to use commands such as "/i 36" or any ids for normally unacquirable technical blocks (Such as piston extensions, door halves, diode baseplates, or otherwise) will be banned on sight, no questions asked. If logs of this are found, same case; instant ban.

Anybody affected by this, please message nillbugwtw for your inventory to be wiped.

Thank you for your cooperation.

 

[SirComputer]

A list of such technical blocks can be found here: http://minecraft.gamepedia.com/Technical_blocks

Please direct any inventory wipe requests to BBPrem or the Administrators. Preferably the former, the latter in extreme circumstances.

 

[Zeus42000]

Is this for the removed ones only, or is it for every technical block, like burning furnaces, Still Water, Nether Portal block, etc?

 

[Hockeyfan1852]

I spawned in 36 by myself to work on a project that uses 36 as a map border so I need my inv cleared as well. :/

 

[Friendy]

Nillbugwtw Is it possible that these broken technical blocks could be added onto a black-list to stop players from being able to spawn them to prevent this from happening?

 

[Lux]

This is only happening because of 1.7 removing many all the technical blocks from the game.

Edit: http://minecraft.gamepedia.com/Version_history#1.7.2

"Many technical block items removed (see Technical Blocks page for complete list)"

 

[Nillbugwtw]

Nillbugwtw Is it possible that these broken technical blocks could be added onto a black-list to stop players from being able to spawn them to prevent this from happening?

I've already blacklisted them all on CommandBook, not sure why it's still possible to spawn them - looking into it. Also, BBPrem, until this is fixed, I've changed permissions to allow you to clear player's inventories. Time it up with whoever's stuck in the lobby, and have /clear playername -a sitting in your chat waiting for them to join. As soon as they join, slam the enter key with the force of 1000 suns and wait. Sometimes it will still kick them, sometimes it won't, but at that point they should be able to rejoin without issue.

 

[Friendy]

Nillbugwtw Is it possible that these broken technical blocks could be added onto a black-list to stop players from being able to spawn them to prevent this from happening?

I've already blacklisted them all on CommandBook, not sure why it's still possible to spawn them - looking into it. Also, BBPrem, until this is fixed, I've changed permissions to allow you to clear player's inventories. Time it up with whoever's stuck in the lobby, and have /clear playername -a sitting in your chat waiting for them to join. As soon as they join, slam the enter key with the force of 1000 suns and wait. Sometimes it will still kick them, sometimes it won't, but at that point they should be able to rejoin without issue.

Perhaps there is still an issue with CommandBook itself that allows users to spawn items in even if they are disallowed as they have permission to spawn in any item - I did have that issue on my own server, never got round to figuring out why it happened or what was causing it.

I would assume that Lava is still disabled for guests? If so, you could always try disabling the technical blocks for guests and if they cannot spawn then them you would know the under-lying issue is to do with the builder rank's permissions.

 

[GmK]

I've already blacklisted them all on CommandBook, not sure why it's still possible to spawn them - looking into it.

Also block with WorldGuard, CommandBook is no good in such an instance.