Closed benjajaja closed 9 years ago
Needs a quick review and I'll merge. @ProgrammerDan @WildWeazel
Any volunteers?
I don't see any obvious errors in the code, can't speak to the logic. Assuming it's a clean compile, I see no reason this can't go to testing unless @WildWeazel has a different opinion!
In any case it'd be great if gipsy wrote up a testing plan in anticipation of the merge; specifically: what changed, what stayed the same, and what testers need to do to activate all the prior.
will do, in discourse will be best I think
ok to test
pumkins and melons' fruit growth is stored as extra field.
Keeping track of fruit growth is more expensive than crops:
There is room for future improvements at Fruits.java as noted in comment.
Cactus and sugarcane will probably use the same principle, but won't need that much block checks, jsut the block above.
Trees don't need to track "fruits" since a sapling only grows once. But I want to move away both from magic-numbers/data-ids for tree types and make the internal [material/treetype/other?] to growthconfig map typesafer.