/quests quit [SUGGESTION]

[agoniaprivat]

What does your feature do?

If config.yml is set to max-quests: 1, removes the requirement to type in the quest name when doing /quests quit.

How would people use it?

Would stop a lot of confusion for players, since we only allows one quest a time.

[PikaMug]

Thanks for the suggestion. I'd consider a pull request for this, but personally I'd rather the player be absolutely certain of which quest it is they're quitting.

[agoniaprivat]

Thanks for the suggestion. I'd consider a pull request for this, but personally I'd rather the player be absolutely certain of which quest it is they're quitting.

Yeah but make so they still have to type "yes" or "no" in chat 👍

Just that they have to put the quest name in the quit command, gets a little bit weird.

[HorusApl]

MyCommand (or similar plugin) can do this. Placeholders can execute themselves via a console command, so doing something like: /questadmin quit $player %quests_player_current_quest_names% would work for your purposes.

[PikaMug]

@agoniaprivat Note that the yes/no prompt can be disabled (config.yml confim-abandon).

@HorusApl I think they want the player to run the command, or do you mean that MyCommand can take the player's /quests quit and "convert" that into a console command?

[HorusApl]

When using MyCommand, it can execute commands by the player as if they had console level perms. So anything you set there will execute even if it's a regular person. Quick example if they decide to use. $player is the internal placeholder that MyCommand uses for the player that can the command. So in this example, it will do exactly as they suggested, but with /quitquest being a shorthand of that

questsalt5: # just the ID that it needs
command: /quitquest # Command the player runs
type: RUN_CONSOLE
runcmd:

• /questadmin quit $player %quests_player_current_quest_names%