SphereServer BugTracker - SphereServer
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0001616SphereServerexecutable - genericpublic22-05-09 15:1922-05-09 17:20
Reporterdzhony 
Assigned To 
PrioritynormalSeverityminorReproducibilityalways
StatusclosedResolutionno change required 
PlatformOSOS Version
Product Version 
Target VersionFixed in Version 
Nightly VersionNot Available
Experimental FlagsNone
Option FlagsNone
Internal Build Number
Summary0001616: [Win32 SVN Nightly]: CClient::addBarkParse error?
DescriptionSphere Version 0.56b-Nightly [WIN32] by www.sphereserver.com, compiled at May 22 2009 (00:02:06), internal build #1140

See included image ..

It seems as if the problem was connected to the latest revision entry, older SVN nightly was working fine.
Notice that line numbers displayed in console doesn't match the script.
The screenshot displays the only use of SYSMESSAGE with @ parameters in the script.
Numbering of the other script files is correct.
Steps To Reproduce
Additional InformationTested after fresh start of SphereServer.
TagsNo tags attached.
Relationships
Attached Filespng messages.PNG (33,086) 22-05-09 15:19
http://tracker.sphere.torfo.org/bugs/file_download.php?file_id=22&type=bug
Issue History
Date ModifiedUsernameFieldChange
22-05-09 15:19dzhonyNew Issue
22-05-09 15:19dzhonyFile Added: messages.PNG
22-05-09 15:19dzhonyNightly Version => Not Available
22-05-09 15:19dzhonyExperimental Flags => None
22-05-09 15:19dzhonyOption Flags => None
22-05-09 17:20MrSugarCubeStatusnew => closed
22-05-09 17:20MrSugarCubeNote Added: 0000230
22-05-09 17:20MrSugarCubeResolutionopen => no change required

Notes
(0000230)
MrSugarCube   
22-05-09 17:20   
Your errors come from you specifying mode '3' for your sysmessage on [your] line 2018. As indicated in the latest revisions mode 3 is now used for localized messages (prior to this change it was unused and would have defaulted to 0 for ascii), so changing it to 0 (ascii) or 1 (unicode) will correct the error.

The line number thing is odd but shouldn't be related to this - my guess would be that there are inconsistent line endings in the file, but as long as the script runs fine i wouldn't be too concerned about it.