Author Topic: Creating Custom Packet Handlers & Limits there of  (Read 1632 times)

fournicknet

  • Newbie
  • *
  • Thank You
  • -Given: 1
  • -Receive: 0
  • Posts: 5
    • View Profile
Creating Custom Packet Handlers & Limits there of
« on: June 26, 2014, 11:07:29 PM »
Aaron,

I'm currently stuck in my project with a feature I'm trying to implement.  I'm trying to add a method / event to a gui interface that will trigger the packet handler to send the packet to the tNet server.  I have done this a number of times with other events so I don't think I'm calling the event incorrectly in code.  The issue that is being exhibited is that the client is sending the custom packet request; but the server is acting like it is not receiving the request.  Is there any limitations on number of custom packets that can be used on server or client?  I know I'm suppose to post some code but before I copy and paste from 6 different places I wanted to just see if there is anything simple that would prevent custom packets from being processed from client / server.

Thanks,

Nick

fournicknet

  • Newbie
  • *
  • Thank You
  • -Given: 1
  • -Receive: 0
  • Posts: 5
    • View Profile
Re: Creating Custom Packet Handlers & Limits there of
« Reply #1 on: June 27, 2014, 12:03:07 PM »
After doing some more diagnostics, found that the server was receiving the custom packets being sent.   The server wasn't able to read them because the TNPacket.cs files didn't have the custom packets in the same order as the client.  This issue has been resolved.