Can not open ticket from console about reportrts HOT 11 CLOSED

Are you using the latest development build?

from reportrts.

Sorry I misunderstood. Legacy commands cannot ever work from console. You gotta do /ticket first, followed by the sub command you have configured.

from reportrts.

I guess you did not see my edit?

I can not use the sudo command to perform any functions of reportrts either in game or from the console. it does not matter if i put ticket in front of it or not. I guess if i have "legacy" mode turned on it must disable the ability to use sudo?

from reportrts.

I don't know what sudo is but if it attempts to execute something as someone I can not guarantee that it will work and I will definitely not work to support it as it is a non-issue. Ultimately you are trying to do something I don't support by attempting to bypass limitations.

from reportrts.

Since you still didnt answer my first question, why wont reportrts allow tickets to be opened from the console I will paste what happens:

[14:05:12 INFO]: [V]<::::Ruez::::> oho
>ticket open testing one two three
>ticket check
[14:05:23 INFO]: --------- 1 Tickets - Open ---------
[14:05:23 INFO]: #200 13 hours ago by austindkelly - Claimed by WillRavon
[14:05:23 INFO]: [ReportRTS] CONSOLE TicketCommand took 0.406ms: ticket check

as you can see the ticket check works but the ticket open does not work from the console.

obviously trying to use modreq from the console simply states unknown command even though we are using "legacy" mode.

from reportrts.

that should explain how and what sudo is.

I know what sudo is in the linux world. But it is not common knowledge that this should be applied in Minecraft.

Whats really frustrating is that before you changed everything this worked just fine. So it would seem that you are blocking the ability for sudo to work (which works with EVERY other plugin I have 35+)

You can try disabling legacy and type the full command to see what happens. I have a feeling that what sudo does is just masking the sender, which is not going to work as it would still be the console sending it.

I dont really understand why every command cant work from the console. Is it becuase you dont WANT commands to work from the console or that you do not KNOW how to get commands to work from the console?

The only commands that are not available are legacy, but that is because you don't have the understanding of what it is despite me telling you several times before.
LEGACY, or let's say "legacy" are not actual commands. Think of it as a CommandHelper Lite Edition that is built in.
All it does is create ALIASES that hooks into the PlayerCommandPreprocessEvent and listens for commands that matches the configured SUB-COMMANDS of ReportRTS. So if you have legacy set to true and type /check (provided your ReadTicket sub-command is set to "check"), then the actual command sent is /ticket check.
You just don't know about it, hence "legacy". As you might know, PlayerCommandPreprocessEvent says Player... and as far as I know Console sure isn't a player. Because of this the console is incapable of listening in on these events and as such will never work.

I dont understand why you keep removing/blocking functionality and then try to say it is better than it was before?

Nothing has changed except from the default command layout. No functionality has been removed or blocked.

This makes me think you have purposefully limited reporrts to not allow things like sudo to work. being able to sudo a reportrts command should NOT be a limitation, it should just work.

Don't be ridiculous.

For starters, a genuine limitation (that I didn't put in place, but actually worked around to allow it to work somewhat in the first place!) is the command /ticket open or previously known as /modreq.
Console does not exist in the game world and as such used to be completely incapable of submitting a ticket because the world and location does not exist.
For my UUID update I even had to write further workarounds to make Console capable of doing almost anything as Console does not have a UUID.

Limitations are there because without them very large and frequent changes would have to be made.

Since you still didnt answer my first question, why wont reportrts allow tickets to be opened from the console I will paste what happens

Looks like you are trying to do /ticket open when you just said yourself that you tried using /modreq from console and it didn't work. You have configured OpenTicket as modreq. Thus you have to type ticket modreq <your message>.

from reportrts.

sudo still does not work ingame properly. but i managed to script a work around (another "LEGACY" alias ) using /ticket modreq blag will work from the console but not ingame, it seems you cant have both working at the same time so i make my own set of aliases using a different plugin and turned legacy mode off and blocked the "ticket" command ingame and passed the player and location infomation though the console. basically going around my ass to get to my elbow but at least now i can sudo reportrts commands from ingame like i could before. it seems odd that you can only select one or the other in terms of legacy mode on or off.

from reportrts.

I can confirm that turning legacy mode to true does not affect the normal command. This I have tested excessively. And on a code level it is incapable of doing anything as all it does is reroute the command to the new ticket command.

from reportrts.

well it must be something permissions based or something odd on my end then because you can not use the ticket command when legacy mode it set to true in-game on my server.

from reportrts.

Plugins could be the cause. I don't know.

As far as I can tell this is not a game breaking issue and I'll take it into account when porting the plugin to Sponge.

At the moment ReportRTS is feature frozen until there is an API to port to.

from reportrts.

++ for porting to sponge glad to hear.

from reportrts.