Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
MythicMobs MythicMobs
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 146
    • Issues 146
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Incidents
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • MythicCraft
  • MythicMobsMythicMobs
  • Issues
  • #925

Closed (duplicated)
(duplicated)
Open
Created Sep 18, 2022 by Adam Parry@aparry91

command & jsonmessage mechanic elevated perms tied to the user

Summary

Current usage of command mechanic, and/or jsonmessage mechanic seems to evidence that the commands are ran by the player triggering the event, rather than via the server. For this reason issues arise such as a normal, non-elevated user trying to interact with the extended gameplay receives an info message from LuckPerms hindering the immersive experience of using MythicMobs and drawing the users attention to the Info message instead.

Please see various attempts of integrating the required functionality here

Result of ClickEvent


Usage This would be usable specifically in the command and/or jsonmessage mechanic to prevent issues of players being tied to the running of commands, i.e. unnecessarily receiving an INFO message


Value

The ability to run the command via console/server instead of as a temporary privileged user would rid of unnecessary INFO messages returning to the player. Additionally it would save time and effort on a wider scale to deal with the issue here rather than users having to reach out to a multitude of different plugin developers to enable silence flags on all commands.


Priority

High


Implementation

This I am not too sure about, however I feel that if it were at all possible to retain the trigger player, but then take that information and run the commands through the server instead of via a player.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking