Advertisement
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Outdated Log Interceptor v0.6

A plugin for developers that detects changes to the console log, and sends packets to broadcast.

PROTOCOL DESCRIPTION
LogInterceptor uses UDP.

Every packet is a string, and at the beginning of each one there is a special identifier.

Packets:
  • PACKET_COMMAND_CONSOLE -> CC
  • PACKET_COMMAND_PLAYER -> CP
  • PACKET_PLAYER_CHAT -> PC
  • PACKET_GAMEMODE_CHANGE -> GC

After the ID, each packet has its own values. Also, to separate data, the - is used. For example, here is a Player Command Packet:
Code:
CP-jython234-spawn
As you can see, the first section is the Packet ID, and then the next one is the player's name. Finally, the last value is the command issued.

You can easily separate this into an array below (PHP):
PHP:
$pktArray explode("-"$packet);
PACKET DOCS:
As of version 0.6


PACKET_COMMAND_CONSOLE:
FieldName Example Value
Packet ID CC
Command say hello

This packet represents a command ran by the console. The first field is the Packet ID followed by the command ran.

PACKET_COMMAND_PLAYER:
FieldName Example Value
Packet ID CP
Player jython234
Command spawn

This packet represents a command ran by a player. The first field is the Packet ID, and then the player's name is specified. Lastly, the command ran is after the player's name.

PACKET_PLAYER_CHAT:
FieldName Example Value
Packet ID PC
Player jython234
Message Hello everyone!

This packet contains a chat message, along with the player's name.

PACKET_GAMEMODE_CHANGE:
FieldName Example Value
PacketID GC
Player jython234
Gamemode survival

This packet contains a name of a player, and the gamemode they switched to.

Thats all the currently implemented packets. Other's will be implemented soon!
Advertisement