Hi escortkeel,

Thanks very much for making such an awesome set of plugins. Your work is greatly
appreciated. I am really excited about the options that the new --exec capability opens up.

I've configured the console (1.4.0), have RemoteBukkit (1.5.0) and can connect normally (no
--exec) and issue commands as expected:

The issue I'm running into is with --exec. I can connect just fine and see "Executed: [my command from --exec switch]" but it does not actually get executed on the remote server:

Is this a syntax issue on my end, or could something else be going on?

Thanks again!

Hi again!

Thanks so much for reporting this bug! I've corrected the issue, but in the process I've had to re-write the RemoteBukkit communication protocol. In doing so most of documentation has been rendered out of date. I don't think I'll be able to correct it all before I go to bed tonight (it is 11.15pm where I live right now), so I might wait until tomorrow before I upload all of the files and go public with the release (there are updated versions of the plugin, as well as both the console and GUI clients).

Again, thanks so much for reporting this bug,
Keeley

I'll have a look at this now. :)

Just a status update. The problem has been identified and I am working on a fix right now.

You are right in saying that the plugin jarfile is missing a main class manifest attribute, but this is intentional as there is no main class! :P

The plugin is designed to be loaded by CraftBukkit when you put it in the plugins directory. The console client jarfile ("remotebukkitconsole.X.X.X.jar") is the file that you need run from the command line.

thaaaaat's embarassing...

everything is working great...thanks again for the help!

No problem! Please let me know if you encounter any other issues! :D

Thanks for such a fast turnaround! Looking forward to trying it. I think the Main-Class property might be missing from the manifest: