well its an easy question . it says unknown type 1037 with length 28 ..what packet is 1037 ??
unknown type 1037
10/27/2011 22:47
shadowman123#1
10/27/2011 23:12
abdeen#2
really i dont know it .
but maybe this will help you.
[Only registered and activated users can see links. Click Here To Register...]
but maybe this will help you.
[Only registered and activated users can see links. Click Here To Register...]
10/27/2011 23:24
shadowman123#3
Conquer Wiki talk about Packet structure but i dont talk about that..i'd like to know what packet is 1037 ??
10/27/2011 23:36
abdeen#4
dose this number appear when you click on something ?Quote:
Conquer Wiki talk about Packet structure but i dont talk about that..i'd like to know what packet is 1037 ??
10/28/2011 03:31
shadowman123#5
Nah ..thats y iam asking.i leave the char for anytime then i come and find that btw Away states Working PerfectlyQuote:
10/28/2011 03:40
_DreadNought_#6
If I remember correctly its one of the quest packets.
10/28/2011 10:19
Spirited#7
how many times is it sent on login / whenever it says it? when does it say it?
10/28/2011 18:44
shadowman123#8
just 1 time and happens when i leave the char for even 1 min without moving ...But i dont think its quest packet ever well i can neglect it and add its packets as Case 1037 { break } but i wanna know what packer is it to be able to add itQuote:
10/28/2011 21:02
Lateralus#9
Sounds like an away status sent client->server to notify that the character is away so the server can send relevant information (to display the (Away) string by the name). What version is this? Note: I have very little experience with post-50xx packets, so I can't be much help.
Edit: My bad; didn't notice you said that the away status is working perfectly.
Edit2: After analyzing the current client with a debugger...
ushort @ offset 0 - size 0x14
ushort @ offset 2 - type 0x40D
byte @ offset 4
uint @ offset 8
uint @ offset 12
uint @ offset 16
The routine that calls for the packet to be created is at 0x667117 in the newest client. It's sent every 30 minutes. One of those parameters is a timestamp.
It's also sent server->client. I don't have have enough information to determine what it does and how it processes it because I don't feel like doing this. Try sending some packets back with varying values and see how (or if) the client interprets them.
Edit: My bad; didn't notice you said that the away status is working perfectly.
Edit2: After analyzing the current client with a debugger...
ushort @ offset 0 - size 0x14
ushort @ offset 2 - type 0x40D
byte @ offset 4
uint @ offset 8
uint @ offset 12
uint @ offset 16
The routine that calls for the packet to be created is at 0x667117 in the newest client. It's sent every 30 minutes. One of those parameters is a timestamp.
It's also sent server->client. I don't have have enough information to determine what it does and how it processes it because I don't feel like doing this. Try sending some packets back with varying values and see how (or if) the client interprets them.
10/29/2011 05:28
Spirited#10
It might have to do with daily quests. I can't check atm because I don't have a working laptop. It might be checking all events that are going on on the day of the time stamp.
Edit: Wait... i'm thinking of another packet starting with 11. I opened my packet handler's cs file in notepad... I doubt* that it's the mentor system (packets 1034-1036).
Edit: Wait... i'm thinking of another packet starting with 11. I opened my packet handler's cs file in notepad... I doubt* that it's the mentor system (packets 1034-1036).
10/29/2011 10:15
pro4never#11
it definitely has to do with quests and is sent based on a periodic time.
My guess agrees with the 'daily quests' suggestions.
I would ignore it unless you find a reason to actually use it.
If your server is working properly and there's no missing features (that you haven't started working on) then I would ignore the packet. It's simply the client requesting something (either something to do with time based quests or something to do with automated bot checks. Either way not something you need to worry about right now)
My guess agrees with the 'daily quests' suggestions.
I would ignore it unless you find a reason to actually use it.
If your server is working properly and there's no missing features (that you haven't started working on) then I would ignore the packet. It's simply the client requesting something (either something to do with time based quests or something to do with automated bot checks. Either way not something you need to worry about right now)
10/29/2011 17:06
shadowman123#12
well thx alot im gonna ignore it as it doesnt affect any feature in gameQuote:
My guess agrees with the 'daily quests' suggestions.
I would ignore it unless you find a reason to actually use it.
If your server is working properly and there's no missing features (that you haven't started working on) then I would ignore the packet. It's simply the client requesting something (either something to do with time based quests or something to do with automated bot checks. Either way not something you need to worry about right now)
#request Close