Imported from legacy Flarum.
Original author: coffee (Flarum #668)
Create a command for the character not to move
Imported from legacy Flarum.
Original author: myntsu (Flarum #1047)
What would be the purpose/usage for this?
What would happen in a situation where a skill moves you, or a mob pushes you?
Imported from legacy Flarum.
Original author: sakura (Flarum #1074)
+1
This is useful when you’re refining (whitesmith) / brewing (alchemist) when you want to hold down turbo key.
Imported from legacy Flarum.
Original author: dadalin212 (Flarum #801)
+1, it’ll also complement nicely with classes that use turbo to spam land skills at a single location by locking them down and prevent any unintentional movements (eg EM skill spamming while staying inside land protector).
Imported from legacy Flarum.
Original author: coffee (Flarum #668)
@myntsu You’ve probably never played mecha or genetics 
Imported from legacy Flarum.
Original author: myntsu (Flarum #1047)
@coffee It was a legit question. 
Imported from legacy Flarum.
Original author: jinbou (Flarum #618)
This is useful when you’re refining (whitesmith) / brewing (alchemist) when you want to hold down turbo key.
You can just… either move inventory to the middle of the screen, to where the brew skill popup appears, so that you don’t click the ground when spamming turbo. Or stay next to a wall so that you won’t be able to move
I play meister/biolo and I’ve never felt the need for something like this. imo sounds unnecessary and a waste of dev time
Imported from legacy Flarum.
Original author: SpaceHelm (Flarum #274)
@myntsu u will still get pushed / knockback,
It just to prevent you to move by clicking.
Its usefull whenever you want to spam skills, but dorsnt want to move. Since while spamming smartcast, there is a chance u might move when u combine it with other selfcast skill.
Imported from legacy Flarum.
Original author: coffee (Flarum #668)
@jinbou Or instead of using any of these alternatives.. one can simply use a command: @hold 
Imported from legacy Flarum.
Original author: sakura (Flarum #1074)
@jinbou its QoL improvement for a reason, moving the UI / moving to a “spot” every time you want to use a skill is rather cumbersome. I’d rather just type @hold and leave UI alone. Just like how i never knew i needed @getall command before using it.
Imported from legacy Flarum.
Original author: jinbou (Flarum #618)
@getall, @storeall, @restock, @unequipall etc make me waste at least 5 minutes less each day, they’re real lifesavers and the difference they make is massive. I don’t think they’re comparable to what @hold would provide.
You say “every time you use a skill” but pharmacy is not a skill like MT, cart boost etc that we use all the time, it’s not used often at all. People only brew things seldomly, and under the safety of the town, since the entirety of the brewing process, together with the preparations and casting, take a considerable amount of time.
Doing one of the two things I suggested before starting brewing literally takes half a second. Hell, using @hold command twice would take that time too anyway, so would this change actually reduce the time we spend at all? Do we really need a dev update to reduce the brewing time by like 0.0001%?
Sure, it’s just a harmless QoL suggestion, and I’m probably looking very mean right now by opposing it this harshly. But its a suggestion that would be used by very few people, and would only increase the efficiency of those people by like a second per week, at most… It’s not like this server has an infinite resource of developers, if there was a project manager, they’d look at the benefit it’d bring vs limited resources it’d take, and it’d be rejected on the spot. That’s just how it is. Maybe muh will do it out of the goodness of his heart anyway, which is fine, I don’t care. But it’s just not needed, dev time would be better spent on any other suggestion, which is why -1 from me
Imported from legacy Flarum.
Original author: Akin (Flarum #861)
I normally have to use some narrow lane to stop my crafter from moving. I would love to have this.
Imported from legacy Flarum.
Original author: coffee (Flarum #668)
@jinbou What a boring guy.. the guy making a huge fuss over a suggestion for a simple command that would only benefit the players. If you don’t like the suggestion, just argue with really pertinent questions and don’t express your opinion as if the game were your friend.
Leave it to the GM himself to say whether this will be a lot of work or not, my friend.
Imported from legacy Flarum.
Original author: jinbou (Flarum #618)
@coffee I’m arguing that this feature doesn’t actually help players, and I’m disagreeing because I want other suggestions that actually would benefit players to be implemented instead. It doesn’t matter how much time it takes, it’s still a waste of time
Imported from legacy Flarum.
Original author: coffee (Flarum #668)
@jinbou But from the comments, only you share this negative opinion. The other players liked the suggestion.
Imported from legacy Flarum.
Original author: Muh (Flarum #1)
Suggestions should rather be discussed without worrying about dev time. Should it be something with little use but high dev time it would surely be put on lower priority.
Sometimes changes sound like they could be a lot of work but are done quick and other times simple sounding suggestions are actually a lot of work.
We’re trying to find a good way to prioritze these.
So try to look more if it’s something that helps/fits us
Imported from legacy Flarum.
Original author: jinbou (Flarum #618)
@coffee So? That’s why those players are giving their positive opinion, and I’m giving my negative opinion, what’s the problem here?
I’m saying there are multiple other methods that allow you to achieve the same thing as this command, in the same time. I haven’t seen a use case example here of how this command would help the players better than the existing methods, so as far as I’m concerned, this suggestion doesn’t have any negatives, but it also doesn’t have any positives. And I have no reason to agree to a suggestion if I don’t see any positives to it.
Imported from legacy Flarum.
Original author: MadMonkey (Flarum #165)
Tbf, isn’t @hold supposed to be part of the LGP?
I don’t think I ever saw one available without the other.
Imported from legacy Flarum.
Original author: coffee (Flarum #668)
@jinbou You personally don’t see any reason to implement this suggestion. However, you are offering several different ways to avoid using @hold .. this means that the command is necessary to make life easier for those who: create potions, use duo for buffs, refine gears, etc.
If your only mission here on the forum is to criticize other players’ suggestions, why not try using common sense? What doesn’t work for you… may work for other players.
Imported from legacy Flarum.
Original author: jinbou (Flarum #618)
@coffee
However, you are offering several different ways to avoid using @hold .. this means that the command is necessary to make life easier
That… doesn’t make sense? It’d only make sense if this command was easier or more efficient to use than the existing alternative methods. But that’s the part I was disagreeing with anyway.
Anyway, I don’t understand why you’re getting so upset about my disagreement with the suggestion to the point of making rude personal remarks. No I’m in this forum to discuss suggestions, sometimes I agree with them, sometimes I disagree with them, sometimes I say I’m neutral about them, sometimes I post my own suggestions. I’m just giving my feedback, you don’t need to take every post disagreeing with your suggestion personal. Just let everyone speak their mind, and muh will decide in the end