- %variable% variables can be declared in the INI file and used
elsewhere
- Default argument 'true' for WriteLineFormatted in ConsoleIO
- Exceptions thrown by bots no longer disconnect from the server, stack
trace is printed instead
- Re-add support for MC 1.6 chat color names
- Re-add support for MC 1.5- vanilla whispers in ChatBot
- Add /connect in main chat prompt (reported by TNT-UP)
- Automatically close on connection lost or other failure
- Feature suggested by TorchRJ_
- Also, forgot to mention in 'App refactoring almost done' :
- Issue depending on username and/or server should be fixed
- Created specific namespaces and folders for each app brick
- Added proxy support using Starksoft's Biko Library
- App bricks: Main, ChatBots, Crypto, Protocol, Proxy
- Each class is now in its own file (Aes streams, chatbots)
- Used "Bridge" design pattern for Crypto, Protocol, Proxy
- Added back support for Minecraft 1.4.6 to 1.6.4 (MCC 1.6.2)
- Need to fully re-test everything and fix bugs
- To Fix : Server pinging is slow on SpigotMC
- To Do : Add Minecraft 1.2.5 (MCC 1.3) and maybe 1.3 to 1.4.5
- Player is automatically respawned when logging in
- Added /respawn command (MC 1.7 does not fail to respawn)
- Cleaned MCC command handling code, /exec is now /script
Allow the GUI to pass a request to the console client, not to the
server.
Any string starting with a null character is handled by the console:
Command is: \0commandname\0commandarg
Output from console: \0commandname\0result
eg. \0autocomplete\0/he -> \0autocomplete\0/help
Currently, only "autocomplete" command is implemented.
- Added a notification message when you die stating you can respawn with
/reco
- Added a respawn packet sent before disconnecting when using /reco
Note: Why a respawn in /reco and not a /respawn command? Once respawned
using the console on 1.6.2 server, the player stays invisible for other
players unless he (or the other player) disconnects & reconnect so it's
necessary to reconnect after respawning.
Do NOT put thread sleeps in bots. NEVER. Initialize() and Update() are
called in the main thread!
Also, a delay should be respected between each chat/command sendind to
avoid being kicked.
Putting Thread.Sleep() in bots may cause the client to be out of sync
with the server or make it lose connection so again do not use them :)