SphereServer BugTracker - SphereServer
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0001779SphereServerexecutable - linux buildpublic16-07-10 19:4725-10-10 16:49
Reportertrinax 
Assigned ToMrSugarCube 
PrioritynormalSeveritymajorReproducibilityalways
StatusclosedResolutionno change required 
PlatformOSOS Version
Product Version0.56c Nightly 
Target VersionFixed in Version 
Nightly VersionNot Available
Experimental FlagsDiagonalWalkCheck, New_Triggers, AllowTelnetPacketFilter
Option FlagsFileCommands, NoHouseMuteSpeech
Internal Build Number
Summary0001779: CRITICAL error on startup in sphere(world|chars).scp
Description05:19:CRITICAL:(sphereworld.scp,2587)Error Pri=2, Code=0, Desc='CTileItemType.ReadInfo: TileData Read', in GetItemData
05:19:CRITICAL:(sphereworld.scp,60260)Error Pri=2, Code=0, Desc='CTileItemType.ReadInfo: TileData Read', in GetItemData

The line in the save file includes some "multi" items like ship or house. When I remove the error objects from the file, new ones appear.
Steps To Reproduce
Additional InformationDoes not occur in nightly, it occurs in svn.

Using UO:ML's tiledata.mul after a fresh install, modified.
TagsNo tags attached.
Relationships
related to 0001657resolved MrSugarCube Item Slots Not Readed By Sphere 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
16-07-10 19:47trinaxNew Issue
16-07-10 19:47trinaxNightly Version => Not Available
16-07-10 19:47trinaxExperimental Flags => DiagonalWalkCheck, New_Triggers, AllowTelnetPacketFilter
16-07-10 19:47trinaxOption Flags => FileCommands, NoHouseMuteSpeech
16-07-10 22:19xantierNote Added: 0000513
16-07-10 22:48trinaxNote Added: 0000514
16-07-10 22:50xantierNote Added: 0000515
16-07-10 22:56trinaxNote Added: 0000516
16-07-10 23:07xantierNote Added: 0000517
16-07-10 23:22trinaxNote Added: 0000518
16-07-10 23:22trinaxNote Edited: 0000518
17-07-10 00:09xantierNote Added: 0000519
17-07-10 08:32trinaxNote Deleted: 0000518
17-07-10 08:32trinaxNote Deleted: 0000516
17-07-10 08:32trinaxNote Deleted: 0000514
17-07-10 09:15xantierNote Deleted: 0000519
17-07-10 09:15xantierNote Deleted: 0000517
17-07-10 09:16xantierNote Deleted: 0000515
17-07-10 12:42trinaxNote Added: 0000522
17-07-10 12:58trinaxNote Added: 0000523
17-07-10 17:16trinaxNote Added: 0000524
21-07-10 02:19MirravinNote Added: 0000525
31-07-10 18:23trinaxNote Edited: 0000524
25-10-10 16:48MrSugarCubeRelationship addedrelated to 0001657
25-10-10 16:49MrSugarCubeNote Added: 0000722
25-10-10 16:49MrSugarCubeStatusnew => closed
25-10-10 16:49MrSugarCubeAssigned To => MrSugarCube
25-10-10 16:49MrSugarCubeResolutionopen => no change required
14-11-10 19:54MrSugarCubeCategoryexecutable - linux => executable - linux build

Notes
(0000513)
xantier   
16-07-10 22:19   
common problem but harmless
(0000522)
trinax   
17-07-10 12:42   
I could not login into game because of the logon problem but know I tried it in windows and;

in SVN, I cannot see the houses, instead I see a white dot (like the ones when you do .debug 1) but the doors can be seen. Tried both [multidef] and [itemdef] (the old one I have) versions of the multi files, cannot see for both.

in latest Nightly, everything is okay, no errors and the houses are there.
(0000523)
trinax   
17-07-10 12:58   
Additional feedback: the problem is not there on a fresh windows SVN sphere.
(0000524)
trinax   
17-07-10 17:16   
(edited on: 31-07-10 18:23)
I have found and fixed the problem, it was about some multiple declaration of multis in my scripts.
(0000525)
Mirravin   
21-07-10 02:19   
I have fixed multi, but sometimes I get errors:

03:37:CRITICAL:Error Pri=2, Code=107, Desc='CTileItemType.ReadInfo: TileData Read', in GetItemData
20:09:CRITICAL:Error Pri=2, Code=22, Desc='CTileItemType.ReadInfo: TileData Read', in GetItemData

Code 22 and 107 only. Somebody know, what can be the reason? Or what it really means?
Sphere: Linux, Build: #1296.
(0000722)
MrSugarCube   
25-10-10 16:49   
The error itself is caused by a failed attempt at reading an entry from tiledata.mul.

If the problem only appears after using the automated builds, the likely cause is that there are still item scripts that haven't been updated. All item scripts whose ID is greater than 0x3FFF must be updated to use the new range, not just multis.