Render Display Entity #251
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
ThreeTAG/Palladium#251
Loading…
Reference in a new issue
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?
Currently, using render layers or powers outside of players (for instance, for a stationary placed attack) requires the use of armor stands. This is fine, but does sometimes lead to issues.
Instead, it would be great if there could be a Render Display entity, similar to how vanilla has Item/Block/Text Displays. These would have no hitbox and be invisible like the vanilla displays, and instead appear as one (or multiple) render layers specified in NBT.
It would also be great if these could have powers, because then armor stands wouldn’t need to be used at all.
Reported by @legobrick22 via Discord — open thread
What could you do with a display entity that's not possible with armor stands?
StephaTea (@stephatea.) via Discord — jump to message
There’s nothing new, it just makes what’s already possible easier and cleaner.
No need to worry about hitboxes, anything that might interact with armor stands, or stuff like that. If it’s just the render layer, then you don’t need to make a whole power and power renderer for it since you could just specify it in nbt data and save a lot of bloat.
@legobrick22 via Discord — jump to message