-
Notifications
You must be signed in to change notification settings - Fork 13
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
Additional feature request for [camera.offset.multiplier] #194
Comments
Thank you for the suggestion. This will be part of the next release, since it was very easy to implement. Note that this multiplier will be applied whenever the player is holding or using an adaptive item (as configured in the config file). If |
Ooh, yeah. That's very smart. Thanks so much for your suggestion and for accepting mine! Could you please tell me if this works if I don't want my character to be transparent at 0.0 X position, but I want this feature to remain, for example, when I run under trees or something else is above me? Because now I turned off this option, because my character becomes transparent forever. |
Unfortunately, this is not possible, as the transparency is directly dependant on the distance between the crosshair and the center of the player. |
By the way, while the update with this isAiming feature is not out yet, will you be able to make a smooth transition between offsets? As far as I understand, you can't make a transition between first-person and third-person camera, but here only the third-person camera changes position. So, theoretically, it is possible? |
Offset changes within the shoulder surfing perspective use interpolation. See existing offset multipliers or ladder centering. |
There are currently 2 multipliers available:
I propose to add a new type of multiplier:
The camera is shifted to the specified XYZ coordinates during aiming with bow, crossbow, trident and other items that have RMB action (for example, staffs from RPG Series mods).
Below I'll show screenshots of what it should look like (roughly).
The text was updated successfully, but these errors were encountered: