Skip to content
This repository was archived by the owner on Nov 9, 2017. It is now read-only.

Conversation

@Tonodus
Copy link
Contributor

@Tonodus Tonodus commented Nov 12, 2014

This should fix #527 expect that blocks with hardness 0 won't be dropped (redstone, redstone torches, torches, flowers, etc).

I'm not 100% sure I've added all known cases, I will go through any cases when #527 or this is updated.

@turt2live
Copy link
Contributor

PRHOLD: Mapping of vanilla values. See doc

@turt2live
Copy link
Contributor

@Tonodus You broke the tests with your last commit.

@Tonodus
Copy link
Contributor Author

Tonodus commented Nov 13, 2014

@turt2live dammit... fixed.

@turt2live
Copy link
Contributor

@Tonodus This pull request is no longer mergeable. Please resolve the issue as soon as possible, thanks!

@dequis
Copy link
Contributor

dequis commented Jan 16, 2015

The hold for this one isn't really needed, is it? Because I suspect it might be a while until the spreadsheet covers absolutely everything

@turt2live
Copy link
Contributor

I actually completely forgot about that spreadsheet. I'll work on a better way to generate a list of values though because manual methods are... hard.

deathcap referenced this pull request in GlowstoneMC/Glowstone Apr 6, 2015
#540

Conflicts:
	src/main/java/net/glowstone/block/ItemTable.java
	src/main/java/net/glowstone/block/blocktype/BlockSapling.java
@turt2live turt2live removed their assignment Feb 7, 2017
puigru pushed a commit to puigru/Glowstone-Legacy that referenced this pull request Aug 30, 2017
* Revert back to the old Java 8 classpath behavior because of Java 9 delays

* Add new libraries for increased compatibility
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Bad drop mappings

4 participants