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

Suggestion: Arbitrary block to arbitrary block custom plants #10

Open
GavJenks opened this issue Dec 31, 2019 · 3 comments
Open

Suggestion: Arbitrary block to arbitrary block custom plants #10

GavJenks opened this issue Dec 31, 2019 · 3 comments

Comments

@GavJenks
Copy link

For example, a violet tulip which matures into a lilac plant which I might call "flax" and then make drop wool. Or a vine matures into a purple wool "grape" or a azure bluet matures into a peony which i've reskinned into cotton.

I think the way RB works (?) is to have a collection of plant locations loaded and running a timed pass over them now and then, then comparing timestamps on chunk loading. If so, there's no need for the plant to be an actual minecraft plant, is there? It might not be very much extra work to allow configurable custom from:to plant types that could triple or quadruple the gameplay latitude of the plugin almost overnight.

@ProgrammerDan
Copy link

See, this is awesome. But definitely more for CropControl -- this is an explicit desire for CropControl in terms of expansion / improvements.

@ProgrammerDan
Copy link

Let me expand on that. Realistic Biomes isn't about maturation cycles but rather maturation time. CropControl is explicitly about maturation cycles AND drop control, which is explicitly what you are describing. Instead of bloating Realistic Biomes, we made CropControl to do exactly what you are describing, but initial implementation just wraps currently available crops; future implementations should include exactly what you are describing (custom growth patterns w/ custom drops, etc).

@ProgrammerDan
Copy link

I think the way RB works (?) is to have a collection of plant locations loaded and running a timed pass over them now and then, then comparing timestamps on chunk loading.

Not exactly, should have mentioned that. It does do timestand comparing and blending to control / prevent growth cycles, but only for existing plants that trigger their own maturities. And even then, quite limited. Def something more suited for CropControl, which already has deep growth cycle settings and it would be a pretty natural extension to allow for custom growth types, natures, and drops.

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

2 participants