SphereServer BugTracker - SphereServer
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0001691SphereServerexecutable - genericpublic19-12-09 00:5902-01-10 03:46
ReporterTerrikate 
Assigned ToMrSugarCube 
PrioritynormalSeverityblockReproducibilitysometimes
StatusresolvedResolutionfixed 
PlatformOSOS Version
Product Version0.56c Nightly 
Target VersionFixed in Version0.56c Nightly 
Nightly VersionNot Available
Experimental FlagsNone
Option FlagsNone
Internal Build Number
Summary0001691: Strange problem with the journal
DescriptionBuild #1186

Sometimes, updated journal stops, and if you move or try to expand its size, produce the client crash.
Steps To Reproduce
Additional InformationI will try to provide more information if I find a SpyUO that works in client 2.0.3
TagsNo tags attached.
Relationships
related to 0001869resolved MrSugarCube Sphere sends malformed ASCIIMessage (1C) Packet 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
19-12-09 00:59TerrikateNew Issue
19-12-09 00:59TerrikateNightly Version => Not Available
19-12-09 00:59TerrikateExperimental Flags => None
19-12-09 00:59TerrikateOption Flags => None
01-01-10 18:39TerrikateNote Added: 0000342
01-01-10 18:40TerrikateNote Edited: 0000342
01-01-10 18:41TerrikateNote Edited: 0000342
02-01-10 03:46MrSugarCubeStatusnew => resolved
02-01-10 03:46MrSugarCubeFixed in Version => 0.56c Nightly
02-01-10 03:46MrSugarCubeResolutionopen => fixed
02-01-10 03:46MrSugarCubeAssigned To => MrSugarCube
02-01-10 03:46MrSugarCubeNote Added: 0000343
21-12-10 02:10MrSugarCubeRelationship addedrelated to 0001869

Notes
(0000342)
Terrikate   
01-01-10 18:39   
(edited on: 01-01-10 18:41)
Firstly Happy New Year.

In the end I got some time and have watched what's the problem. The problem is that messages SpeechType 0x06 system, when they show the name of an NPC is long doesn't deliver the necessary line breaks. Then if you move the journal client crash.

ASCIIMessage(1C)

Old version

GOOD
- Text: "DONT REMOVE"
- SpeechType: "0x6"
- Hue: "0x26"
- Font: "3"
- SourceName: "DONT REMOVE"
- Serial: "0xE5104"
- ModelId: "0x3"

0000: 1C 38 00 00 0E 51 04 00 03 06 00 26 00 03 44 4F .8...Q.....&..DO
0010: 4E 54 20 52 45 4D 4F 56 45 00 00 00 00 00 00 00 NT REMOVE.......
0020: 00 00 00 00 00 00 00 00 00 00 00 00 44 4F 4E 54 ............DONT
0030: 20 52 45 4D 4F 56 45 00 -- -- -- -- -- -- -- -- REMOVE.

GOOD
- Text: "DONT REMOVE DONT REMOVE"
- SpeechType: "0x6"
- Hue: "0x26"
- Font: "3"
- SourceName: "DONT REMOVE DONT REMOVE"
- Serial: "0xE5104"
- ModelId: "0x3"

0000: 1C 44 00 00 0E 51 04 00 03 06 00 26 00 03 44 4F .D...Q.....&..DO
0010: 4E 54 20 52 45 4D 4F 56 45 20 44 4F 4E 54 20 52 NT REMOVE DONT R
0020: 45 4D 4F 56 45 00 00 00 00 00 00 00 44 4F 4E 54 EMOVE.......DONT
0030: 20 52 45 4D 4F 56 45 20 44 4F 4E 54 20 52 45 4D REMOVE DONT REM
0040: 4F 56 45 00 -- -- -- -- -- -- -- -- -- -- -- -- OVE.

GOOD
- Length: 80
- Text: "DONT REMOVE DONT REMOVE DONT REMOVE"
- SpeechType: "0x6"
- Hue: "0x26"
- Font: "3"
- SourceName: "DONT REMOVE DONT REMOVE DONT R"
- Serial: "0xE5104"
- ModelId: "0x3"

0000: 1C 50 00 00 0E 51 04 00 03 06 00 26 00 03 44 4F .P...Q.....&..DO
0010: 4E 54 20 52 45 4D 4F 56 45 20 44 4F 4E 54 20 52 NT REMOVE DONT R
0020: 45 4D 4F 56 45 20 44 4F 4E 54 20 52 44 4F 4E 54 EMOVE DONT RDONT
0030: 20 52 45 4D 4F 56 45 20 44 4F 4E 54 20 52 45 4D REMOVE DONT REM
0040: 4F 56 45 20 44 4F 4E 54 20 52 45 4D 4F 56 45 00 OVE DONT REMOVE.

Latest version (build # 1186)

BAD
- Length: 80
- Text: "DONT REMOVE DONT REMOVE DONT REMOVE"
- SpeechType: "0x6"
- Hue: "0x26"
- Font: "3"
- SourceName: "DONT REMOVE DONT REMOVE DONT "
- Serial: "0x2B27FA8"
- ModelId: "0x3"

0000: 1C 50 00 02 B2 7F A8 00 03 06 00 26 00 03 44 4F .P........&..DO
0010: 4E 54 20 52 45 4D 4F 56 45 20 44 4F 4E 54 20 52 NT REMOVE DONT R
0020: 45 4D 4F 56 45 20 44 4F 4E 54 20 00 44 4F 4E 54 EMOVE DONT .DONT
0030: 20 52 45 4D 4F 56 45 20 44 4F 4E 54 20 52 45 4D REMOVE DONT REM
0040: 4F 56 45 20 44 4F 4E 54 20 52 45 4D 4F 56 45 00 OVE DONT REMOVE.
(0000343)
MrSugarCube   
02-01-10 03:46   
Nice find. :)

I think your GOOD and BAD packets are the wrong way around, but confirmed and fixed. :P (interesting that the client only seems to run into the problem with this packet and only for type 0x06)