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

Workspace regions should indicate angles #9

Open
haykam821 opened this issue Aug 30, 2022 · 3 comments
Open

Workspace regions should indicate angles #9

haykam821 opened this issue Aug 30, 2022 · 3 comments

Comments

@haykam821
Copy link
Contributor

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, or Pitch 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 to FrameRotation.

@Restioson
Copy link
Contributor

Is there a reason that this should not simply be a per-minigame thing?

@haykam821
Copy link
Contributor Author

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.

@Restioson
Copy link
Contributor

Restioson commented Jun 11, 2024

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 #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?

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