Solved Command Priority

Hello all,
I am creating a plugin that recreates some commands used in popular plugins. Is there a way to have my command execute first? I've tried the Preprocess command thing, but it executes my command and the other one. If you know of a way of not using the Preprocess thing, please tell me. If there is no way, can you help me figure out the Preprocess thing.

EDIT: It is the PlayerCommandPreprocessEvent

 

@AngryCupcake274 No, that is not what the intent of the event is for. Read this post about event priorities.

 

@ShadowLAX I am creating the new command, and need to stop the other one from happening. Even on MONITOR, the other one still called first.

 

@AngryCupcake274 My apologies I misled you, those are for events not commands. You can't stop a command another plugin has already registered, so you need to change the name of your command.

 

@ShadowLAX For everyone needing help with this, here's a link.
http://bukkit.org/threads/getting-your-priorities-straight-the-plugin-version.788/
Summary:
EventPriority.LOWEST gets called first, now EventPriority.HIGHEST

@ShadowLAX I still wish that EventPriority.HIGHEST was called first. It makes more sense for coding....

EDIT by Timtower: merged posts

 

@AngryCupcake274, uhh, no it doesn't. Having it lowest means it has the last say over canceling the event.

 

@Tecno_Wizard Nope. Read the link.

I know it makes no sense....but....

 

You could just get Bukkit's command map and unregister commands you are overriding before adding your own

 

@AngryCupcake274, i realized i typed that incorrectly. By having the priority the highest, it is called last, giving it final authority over the result of the event. Monitor is true last so the final result can be determined, hence the name monitor. It is not supposed to change the result.

As far as stopping the command, put the command IN the preprocess event (this is a horrific practice, but it's necessary for this) and cancel the event.