Allow dynamically adding several types of border and opening blocks #8
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: EpicKnarvik97/Stargate#8
Loading…
x
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
It would probably be possible to allow the usage of several types of blocks in a single gate border. By allowing users to define things like: a=GLASS, and then adding that to the list of border blocks, the gate layout could probably be read as usual.
There probably needs to be some restrictions on which characters can be used for what, especially if custom gate-open blocks should be a thing.
For easier parsing and less confusing, custom additional materials could be defined like: custom-border-k=GLASS, custom-opening-open-f=GLOW_LICHEN and custom-opening-closed-l=OAK_PLANKS.
I'm not sure whether this would have a big impact performance-wise. Probably not, as long as it's implemented correctly.
For border blocks, it seems this already works, though it is not documented. Testing it, it seems to work with a=GLOWSTONE to create a two-material stargate. For open and closed blocks, it would require to rewrite the general logic of how it works, so it might not be the best idea.