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

More configurable auto generation #173

Open
TheEpicBlock opened this issue Jun 19, 2022 · 1 comment
Open

More configurable auto generation #173

TheEpicBlock opened this issue Jun 19, 2022 · 1 comment
Labels
A: discussion C: poly generation Issues related to the automatic generation of polys

Comments

@TheEpicBlock
Copy link
Owner

The way the current poly generation works has bugged me for a while. It's currently impossible to reorder the way blocks are assigned. PolyMc will always fill in the missing entries using the BlockGenerator. The easiest way to get around this is to make a custom Polymap but that has a number of flaws in it. Polys registered using the api only get added to the default polymap and PolyMc's (and Polymer's) resource generation (and the PolyDump method) only operate on the default map.

@TheEpicBlock TheEpicBlock added C: poly generation Issues related to the automatic generation of polys A: discussion labels Jun 19, 2022
@TheEpicBlock
Copy link
Owner Author

A potential thing I'd maybe like to do is have rules. Instead of registering their polys, mods would register a rule that would apply their polys to their blocks. Then the Polymap can choose if it wants to apply that rule. It might be worth incorporating a config system for this in PolyMc.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A: discussion C: poly generation Issues related to the automatic generation of polys
Projects
None yet
Development

No branches or pull requests

1 participant