Procon 2.0 ALPHA will be available here in the forums as a developer release on 16/03/11.

This version will mostly be used by plugin authors to help finalize the first plugin API available in the BETA – which I hope to release on the 1′st of April.

This version will initially support Bad Company 2, Medal of Honor 2010, Call of Duty Black Ops and Homefront. A lot has been done, but a *lot* is still required to meet my expectations of the software.

This will be available for testing and feedback by the community. You guys are the ones that use it, so try it out and help build this software with us. So far the majority of Procon.Core and Procon.Net has been completed, the last piece of the puzzle is Procon.UI (which is always the last thing to be developed).

Net

• Procon now supports multiple games with the foundation to support every game.

Plugins

• Plugins now load compiled assemblies instead of compiling their own (neater code, bigger plugins and easier to collaborate efforts on a plugin)
• Procon now collects all information for a plugin, instead of making a plugin a sub-rcon-application on its own
• Plugins have been designed to allow for growth and expansion at a later date without breaking older plugins
• Plugins in Procon 1.0 are not compatible with Procon 2.0, however the conversion shouldn’t be a massive one if a plugin dev chooses to transfer
• Automatic updates should now just happen in the background
• Now you connect to other procons, so you can edit a remote procon like you were using it locally – no more “Parent layer control”.
• NLP – Tell procon “!Kick everyone from Australia” and it’ll do it. “!you dicks with a ping over 200, gtfo”. “!kick everyone with a ping over 200″. “!ban phogue until the 4′th of august for “teamkilling everyone”". It should open up in game commands to allow for very complex commands but in a natural way. The hope is you “tell procon what you want it to do” instead of memorizing a series of commands.

Permissions

• Teamspeak3 (but cut down a little bit) style groups/permissions/accounts.
• You first create a group, then assign permissions to the group then assign accounts to a group. An account can belong to multiple groups.

UI

• Less confusing between the “Local Layer” and “Parent Layer” (this goes with your other point). All layers act and look as if they are “local”.
• Ability to view multiple game connections at once.
• Customizable (eventually) view – i.e. Chat/Player List only.

Check www.phogue.net