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

MUF FORCE for mlev < 4 as SCARY_MUF_PRIM (SF issue) #633

Open
tanabi opened this issue Jul 6, 2021 · 2 comments
Open

MUF FORCE for mlev < 4 as SCARY_MUF_PRIM (SF issue) #633

tanabi opened this issue Jul 6, 2021 · 2 comments
Labels
enhancement New feature or request
Milestone

Comments

@tanabi
Copy link
Collaborator

tanabi commented Jul 6, 2021

I'd like to see FORCE opened up for muckers with less
than wizbits, with the following restrictions:

M1 and M2 would only be able to FORCE players and
things that the program's owner controls().
The forcelock check for these levels would be: program
dbref, current program uid.
(for M1, that means that the program dbref or the
program's owner's dbref would need to be in the
forcelock, as well as the object to be forced being
controlled by the program's owner.)
(for M2, that means that the program dbref or the
program uid's dbref [as affected by SETUID and HARDUID]
would need to be in the forcelock, as well as the
object to be forced being controlled by the program's
owner.)

M3 would be able to FORCE any player or things owned by
anyone, subject to the forcelock check against:
program dbref
current program uid (as affected by SETUID and HARDUID).

M4 would continue to be able to FORCE anything.

Opening FORCE in this fashion would be a
SCARY_MUF_PRIMS primitive.

@tanabi tanabi added the enhancement New feature or request label Jul 6, 2021
@tanabi tanabi added this to the 7.7 milestone Jul 6, 2021
@aidanPB
Copy link
Contributor

aidanPB commented Jan 26, 2022

Since the removal of SCARY_MUF_PRIMS, this would presumably be controlled/enabled by a GOD-only tuneparam.

@wyld-sw
Copy link
Member

wyld-sw commented Jan 26, 2022

Yeah, the name of the issue was copied from source forge, where it originated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants