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

[Suggestion] Armor stand spectating login #2503

Open
MithrandirCraft opened this issue Feb 11, 2022 · 0 comments
Open

[Suggestion] Armor stand spectating login #2503

MithrandirCraft opened this issue Feb 11, 2022 · 0 comments

Comments

@MithrandirCraft
Copy link

MithrandirCraft commented Feb 11, 2022

What feature do you want to see added?

Adding an optional feature that forces players which are either logging in or registring to spectate within an invisible armorstand, for 0 position and head pitch yaw movement.

Making the armorstand's XYZ EulerAngle's, as well as actually using this login approach or not, configurable.

The suggestion for this system was made by @krusic22 on the AuthMe Discord. But it is unlcear if it's actually feasible to be integrated into AuthMeReloaded.

I tried implementing this myself for a later PR, but found Authme's architecture quite daunting, and couldn't make my code fit properly. So I am now suggesting a more experienced dev to implement this instead.

Here's my initial approach to a class that would set up the Armor Stand for one: https://gist.github.com/MithrandirCraft/a0f2ec81c9e1ef0a9c95e962a66bd487

Are there any alternatives?

Yeah. AuthMe used to have a rather rudimentary head position rollback (I do not know if this is still in place), and also still has a position rollback, both of which are not too good at preventing both types of movements, but do indeed roll them back.

Anything else?

No response

@MithrandirCraft MithrandirCraft changed the title Armor stand spectating login [Suggestion] Armor stand spectating login Mar 9, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

1 participant