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

[Feature Request] [Discussion] Clear Grid Pattern #140

Open
KirinDave opened this issue Jun 19, 2022 · 3 comments
Open

[Feature Request] [Discussion] Clear Grid Pattern #140

KirinDave opened this issue Jun 19, 2022 · 3 comments
Labels
enhancement New feature or request

Comments

@KirinDave
Copy link
Contributor

KirinDave commented Jun 19, 2022

Feature Request: A pattern to clear the current grid without losing the current stack or ravenmind. This pattern should be a nop for circles and artifacts. It should not have any special escaping rules, so it won't cause a grid clear in the middle of an intro/retro pair.

Why This Might Be Good:

We have been playing with a method in the discord we call "Flash Casting" where you store a spell in your ravenmind, and keep a quine on the bottom of your stack that invokes your ravenmind spell. This is a pretty cute way to turn yourself into a trinket that's slightly slower to activate (and an ideal playground for self-modifying spells), but the practical limit of it is that your grid fills up with hermes pretty quick.

Also, when stringing together lots of spell fragments, it is nice to be able to clear the grid to make room for the final assembly and arfactification of the spell. It'd definitely be a quality of life improvement.

Why This Might Be Bad:

One dangerous part about this is precisely that it lets us keep our ravenmind around for a long time. It's been observed that it's safe to put a player you meet into your ravenmind and so long as you don't clear your stack, it stays there. Given the new player range rules, it'd be possible to write a spell that assembles a list of players and then curses them even if they don't write their true name to a focus.

The only practical limitation (and this is a fairly soft limitation) to this is that the grid has a maximum size and eventually you'd run out of grid space to inflict new harm.

@TacocaTYT
Copy link

it would probably have a use in artifacts if it cleared the stack though, as it could be used to discard any access data or preloaded spell effects for large multi step decision making spells. perhaps a limitation of this pattern could be that it turns player references to garbage elements?

@KirinDave
Copy link
Contributor Author

If it cleared the stack, it wouldn't really have any purpose and would invalidate bookkeepers. I also think it's going to be a game of cat and mouse trying to trace through nested data structures looking for player references.

@yrsegal
Copy link
Contributor

yrsegal commented Jul 3, 2022

afaik this deliberately does not exist - grid size is a limitation that's intended. Especially with how it makes holding on to a true name harder.

@yrsegal yrsegal added the enhancement New feature or request label Oct 1, 2022
@github-project-automation github-project-automation bot moved this to 📋 Backlog in Hex Casting Jan 11, 2024
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
Status: 📋 Backlog
Development

No branches or pull requests

3 participants