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

.//repeat <number> command to repeat a chain of commands #2677

Closed
MegaMinerDL opened this issue Dec 14, 2024 · 2 comments
Closed

.//repeat <number> command to repeat a chain of commands #2677

MegaMinerDL opened this issue Dec 14, 2024 · 2 comments
Labels
status:rejected This feature request was rejected. type:feature-request Request for something new

Comments

@MegaMinerDL
Copy link

The Problem

Sometimes I find I have to do a set of commands on repeat on a set of selections, for example I might do:

//stack 1 u -am stone
//shift 1 u
//rep stone dirt

//stack 1 u -am stone
//shift 1 u
//rep stone dirt

//stack 1 u -am stone
//shift 1 u
//rep stone dirt

(...)

A Solution

Instead, a //repeat command would repeat the last specified number of commands (ignoring non-slash messages), e.g.:

//stack 1 u -am stone
//shift 1 u
//rep stone dirt
//repeat 3

This would repeat the previous 3 commands in 1.

Alternatives

Using up and enter keys to try speedrun the repetitive process.

Anything Else?

No response

@MegaMinerDL MegaMinerDL added status:pending Pending acceptance or closure. type:feature-request Request for something new labels Dec 14, 2024
@wizjany
Copy link
Collaborator

wizjany commented Dec 14, 2024

this goes into the category of "belongs in a macro mod, not worldedit" imo

@octylFractal
Copy link
Member

octylFractal commented Dec 14, 2024

I agree with that, I don't think we want to be tracking command history / working on a command history level for this type of thing. I could see it happening if we had more details in our operation level, so that we could easily replay an operation instead of re-parsing a command buffer (which may not even have the same effect when run like that, plus needs async handling for clipboard save/load which would be very difficult). As it stands we don't have an operation history or details in it enough to make that, so I'm going to close this.

@octylFractal octylFractal closed this as not planned Won't fix, can't repro, duplicate, stale Dec 14, 2024
@octylFractal octylFractal added status:rejected This feature request was rejected. and removed status:pending Pending acceptance or closure. labels Dec 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status:rejected This feature request was rejected. type:feature-request Request for something new
Projects
None yet
Development

No branches or pull requests

3 participants