View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0001874SphereServerexecutable - windows buildpublic23-12-10 01:5523-12-10 02:56
ReporterTerrikate 
Assigned ToMrSugarCube 
PrioritynormalSeverityblockReproducibilityalways
StatusresolvedResolutionfixed 
PlatformOSOS Version
Product Version 
Target VersionFixed in Version0.56c Nightly 
Summary0001874: Packet QuestArrow (0xBA)
DescriptionAfter the last change made to this packet the client freezes.

Client 7.0.8.2
Additional Information
>>>>>>>>>> Logging started 23/12/2010 1:42:44 <<<<<<<<<<


01:42:45.9946: Client -> Server 0xAD (Length: 44)
        0 1 2 3 4 5 6 7 8 9 A B C D E F
       -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
0000 AD 00 2C 00 01 25 00 03 45 53 50 00 00 2E 00 61 ..,..%..ESP....a
0010 00 72 00 72 00 6F 00 77 00 71 00 75 00 65 00 73 .r.r.o.w.q.u.e.s
0020 00 74 00 20 00 31 00 2C 00 31 00 00 .t. .1.,.1..


01:42:46.1856: Server -> Client 0xBA (Length: 6)
        0 1 2 3 4 5 6 7 8 9 A B C D E F
       -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
0000 BA 01 00 01 00 01 ......
TagsNo tags attached.
Nightly VersionAutomated (specify build number)
Experimental FlagsNone
Option FlagsNone
Internal Build Number1381
Attached Files

- Relationships
related to 0001865resolvedMrSugarCube Quest Arrow (0xBA) Packet Change 

-  Notes
(0000794)
MrSugarCube (administrator)
23-12-10 02:23

It looks like the 'old' arrowquest packet is being sent for some reason.

Can you double-check that it is build 1381 you're using, and also try '.show clientversion' and .'show reportedcliver.full' to check that the server is seeing the correct version numbers?
(0000795)
Terrikate (developer)
23-12-10 02:31

01:35:Sphere Version 0.56b-Nightly [WIN32] by www.sphereserver.com, compiled at Dec 23 2010 (00:03:04), internal build #1381

show clientversion ->> 7.0.8
show reportedcliver.full ->> 7.0.8.2
(0000796)
MrSugarCube (administrator)
23-12-10 02:41

Could you quickly try these two functions and see which doesn't freeze? Maybe your client still wants the old packet and the program you're using to log packets doesn't log the extra 4 bytes because the client isn't expecting them.


[function arrowquestold]
local.x = 1
local.y = 1
sendpacket 0ba b1 w<local.x> w<local.y>

[function arrowquestnew]
local.x = 1
local.y = 1
sendpacket 0ba b1 w<local.x> w<local.y> d0
(0000797)
Terrikate (developer)
23-12-10 02:48

Right. Old packet works correctly
(0000798)
MrSugarCube (administrator)
23-12-10 02:56

Alright then, updated the minimum client required for the new packet version. :)

- Issue History
Date Modified Username Field Change
23-12-10 01:55 Terrikate New Issue
23-12-10 02:23 MrSugarCube Note Added: 0000794
23-12-10 02:31 Terrikate Note Added: 0000795
23-12-10 02:41 MrSugarCube Note Added: 0000796
23-12-10 02:43 MrSugarCube Relationship added related to 0001865
23-12-10 02:48 Terrikate Note Added: 0000797
23-12-10 02:56 MrSugarCube Note Added: 0000798
23-12-10 02:56 MrSugarCube Status new => resolved
23-12-10 02:56 MrSugarCube Fixed in Version => 0.56c Nightly
23-12-10 02:56 MrSugarCube Resolution open => fixed
23-12-10 02:56 MrSugarCube Assigned To => MrSugarCube


Copyright © 2000 - 2010 MantisBT Group
Powered by Mantis Bugtracker