[Feature]: Add a way to check if user has "Allow objects to log me out" on, and some feedback on the RLVa function @logout #846
Labels
No labels
amd
avatars
bug
builder
cannot-reproduce
crash
epic
feature
from-viewer
gl-removal
known-limitation
monitoring
parity
perf
platform
priority
critical
priority
high
priority
low
priority
medium
provenance
rendering
rt
status
in-progress
status
testing
status
up-next
triage
ui
upstream
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
sky_line/Slipstream#846
Loading…
Add table
Add a link
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?
Environment
Slipstream Beta 1.3.0.13
Description
Currently, Slipstream has a (for now) unique RLVa command on @logout: a command that initiates a cancellable 5s countdown that logs off the user at the end. This command only works if the user has the option "Allow objects to log me out" on.
As of now, there is no way for a script that would use such command to know if the user has that option enabled. If a script would rely on that option being on, it would be useful for it to be able to check if it is, and in case it's not, change its behavior accordingly
Additionally, I feel like the way @logout is implemented is a bit too "polite" compared to the usual standards of RLV functions. In my opinion, part of the fun of RLV is to allow in-game objects or other users to take more control of your viewer's functions. A user has always the option of taking back full control of their viewer by disabling RLV(a), but that requires restarting the viewer entirely: a very detectable process, but not unreasonable for what it does. Meanwhile, @logout not only can be disabled and re-enabled freely at any time, but even when it is enabled, it gives users the option to cancel it at any time, which runs contrary to the aforementioned premise of giving others control of your viewer in my opinion. With the way it's implemented right now, the only usage I see for it is for the users that use RLV for automating control of their viewer.
With that, my suggestion would be:
And either:
Shipped in 1.6.0 Beta 4.