Open haykam821 opened 2 years ago
Is there a reason that this should not simply be a per-minigame thing?
Even if the format isn't a standard part of map templates, I think enough games use map templates with angle data in regions to justify making it part of the tools we have available. Arguably, the functionality we define here can be considered separate from the constraints defined in the Map Templates library, so we wouldn't need to worry too much about setting standards here.
As an aside, the NBT changes introduced in #27 help with knowing the value, but the value still does not get visualized.
I think enough games use map templates with angle data
I agree; I think both Siege and KOTH use it for spawn angle. I'm not sure that it is easier to do it in plasmid than it is to do in the game itself however
As an aside, the NBT changes introduced in https://github.com/NucleoidMC/nucleoid-creator-tools/pull/27 help with knowing the value, but the value still does not get visualized.
Not disagreeing, but I wonder if visualization of the NBT is a maybe more general problem?
While workspace regions currently provide an obvious indication of their bounds, no such feature is available for less-standardized angle data. For example, an arrow hologram could point in the direction specified by the
Angle
,Rotation
,Yaw
, orPitch
fields.One consideration to note is that some regions may use the
Angle
field to provide a value other than float degrees; for example, Last Card uses regions with angles that represent item frame rotation. This issue could be resolved in such mods by simply renaming the field, such as toFrameRotation
.