Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Death by explosion destroys resultant grave and many/all items #327

Closed
upthorn opened this issue Feb 25, 2014 · 16 comments
Closed

Death by explosion destroys resultant grave and many/all items #327

upthorn opened this issue Feb 25, 2014 · 16 comments

Comments

@upthorn
Copy link

upthorn commented Feb 25, 2014

Due to minecraft's explosion mechanics, graves can (and usually will) be hit and destroyed by the same explosion that killed the player death, as can the resultant itemEntities.

The problem is: graves are supposed to make death less punishing on the player, but with this issue, graves make death by creeper, TNT, or ghast more punishing, frequently destroying all items in a way that only voidfall and lavaswimming can do in vanilla minecraft.

@mikeemoo
Copy link
Member

Which version of OpenBlocks are you using?

@upthorn
Copy link
Author

upthorn commented Feb 25, 2014

1.2.5, which your main github page says is current. I also browsed through the code on repository to see if graveblocks explosion resistance had been buffed since release, couldn't find anything.

@Ragnoff
Copy link

Ragnoff commented Mar 7, 2014

having the same issue! Unfortunately absent documantation (perhaps in config) this means that I also lsot a great deal of time trying to figure out what happend. If this is uncorectable perhaps graves should be off by default with a note in config explaining that turning on graves will result in the loss of all items if explosions are permitted to damage blocks.

@CliffracerX
Copy link

Heh, something like that happened to me. The hungry aura nodes from Thaumcraft could eat your grave or items when you break it (which is what happened to me).

In all seriousness though, graves should probably have fairly high explosion resistance and maybe send dropped items straight into whoever broke the grave's inventory. That should be a config option though.

@boq boq mentioned this issue Apr 15, 2014
@Pacane
Copy link

Pacane commented Apr 19, 2014

Any update on this?

@nekojess
Copy link

It looks like cab9ee6 might have fixed this? Can someone verify if it has, and can we maybe get a release pushed? I don't know why this bug isn't Critical, I've lost nearly my entire inventory twice in the past two days, which is more than a little infuriating.

@mikeemoo
Copy link
Member

It's not critical because you can disable graves. We'll push a release when we're ready to do so.

@nekojess
Copy link

Fair enough.

@Razorskills
Copy link

Another fix/nice feature could be to have a config option to make the graves invincible to explosions. But not to a player breaking it. I have been looking for a plugin or mod that could make any block indestructible from everything except from a player breaking it, so that I could use it with the graves. But then I thought maybe I could just ask/request for a config from you guys.

And since this is somewhat the same subject i thought I would throw in another Idea.

@Nagapito
Copy link

Well, seems hungry nodes not also eat the stuff when you break the gravestone but it also eats the gravestone. Just died to one and there was no gravestone there... :(

@HexFlareheart
Copy link

If you were eaten by a hungry node, the node eats your drops anyway; there's basically no chance of getting them back, as OpenBlocks can't put a gravestone on top of an aura node.

Sent from Samsung tablet

-------- Original message --------
From: Nagapito notifications@github.com
Date: 05/15/2014 20:12 (GMT-05:00)
To: OpenMods/OpenBlocks OpenBlocks@noreply.github.com
Subject: Re: [OpenBlocks] Death by explosion destroys resultant grave and many/all items (#327)

Well, seems hungry nodes not also eat the stuff when you break the gravestone but it also eats the gravestone. Just died to one and there was no gravestone there... :(


Reply to this email directly or view it on GitHub.

@zmaster587
Copy link

"It's not critical because you can disable graves." It appears graves cannot be disabled in config using openblocks 1.2.8. However the grave issue still remains

@mikeemoo
Copy link
Member

All blocks can be disabled by setting their id to 0

@zmaster587
Copy link

Thanks! That's nice to know but not very clear.. would it be possible to add that as a comment near the top of the config?

@mikeemoo
Copy link
Member

Iirc it explains this in the guide book. If not, ill make sure it does for next release.

@boq
Copy link
Member

boq commented May 31, 2014

Graves are now much more resistant. Should be fixed.

@boq boq closed this as completed May 31, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests