I'm sure it will be easier to assign a new packet class that will be intreacting with the server.
we could use [Packet265Flans extends Packet] and assign register code to loader to load the intel packet and send weapon/plane/vehicle or even anything we want to the server with using DataInputStream and DataOutputStream, this class would need to be in the stand-alone server working too. this should be easy as well as we have controll over the packet. becuase it should be like 32767 of each packet, and we wont be using that much. as I'm suggestion making it simller to CustomPacket of Forge (Packet250CustomPayload). just it will be flans connector between client & server. this will apply to everything i guess.

I'm with AbrarSyed on this. There's nothing wrong with Packet250CustomPayload, and we don't want FlansMod to modify base code. All types of data can be sent with 250.

Its not editing base classes, did you even read the hole thing ?
Its creating a new packet that is sended, we can use Packet250CustomPayload, because its identical

well.. every mod has its own unique way of reading/writing to Packet250CustomPayload anyways... I know a few mod-makers that have created wrappers for CustomPayload that write in stuff like Int Arrays and stuff for easier usage... I think thats a much better idea than making a Packet256 or something.

No. why??? whats wrong weth using the Packet250 Custom Payload??? adding a new packet means base edits to the netwrok stream reader.

Exactly. No need in making a new packet when the same data can be handled in 250.

Alright.