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

Forcing a wiz to @toadplayer (SF Issue) #639

Open
tanabi opened this issue Jul 7, 2021 · 3 comments
Open

Forcing a wiz to @toadplayer (SF Issue) #639

tanabi opened this issue Jul 7, 2021 · 3 comments
Labels
bug Something isn't working
Milestone

Comments

@tanabi
Copy link
Collaborator

tanabi commented Jul 7, 2021

Attempting to go around the lack of toad player prim via
wizz "@toad whomever" force
crashes the muck.

This code crashes it:

: cleanupguest
5 sleep
me @ "@/guest" getpropstr strlen 0 = if "You're not a guest,
you almost got recycled, fun, fun, keep up the good work"
abort then
me @ awake? 0 > if "You are misusing this program." abort then
prog "_usercount" getpropval 1 - prog swap "_usercount" swap
setprop
forcewizz "@toad " me @ name strcat force
forcewizz "@recycle #" me @ intostr strcat force
;

Figured out it is actually a bug in recycling the leftover
slimy toad left behind.

...

When the command to @toad the player runs, all of that
player's programs should be removed from the timequeue,
including the one that's currently running. Thus, it should
not proceed past the initial @toading.

And if you want the TOADPLAYER primitive, recompile the
server with SCARY_MUF_PRIMS set in config.h.

The best thing to do would be to @force the wizard to run a
program that would @force him to do the toad, and then the
@rec. This would prevent the current program from having
issues.

I'm thinking about how this code is structured, and what
it's supposed to do... not easy, since I don't know the
interpreter that well yet.

@tanabi tanabi added the bug Something isn't working label Jul 7, 2021
@tanabi tanabi added this to the 7.7 milestone Jul 7, 2021
@rec
Copy link

rec commented Jul 7, 2021 via email

@wyld-sw
Copy link
Member

wyld-sw commented Jul 7, 2021

Once I found this out, I started trying to enclose those commands in backticks, like @who. I think this suppresses the notification... I don't always remember though!

@tanabi
Copy link
Collaborator Author

tanabi commented Jul 7, 2021

Sorry about that! I was copying a ton of issues over from an old SF project and unfortunately our system's commands feature the @ symbol all over the place. I probably should have escaped the whole thing in backticks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants