0002300: Can't read SERV.MAP[x] value - SphereServer BugTracker

View Issue Details [ Jump to Notes ]

[ Issue History ] [ Print ]

Project

Category

View Status

Date Submitted

Last Update

0002300

SphereServer

executable - windows build

public

29-03-14 03:09

29-03-14 16:13

Reporter

Coruja

Assigned To

Ben

Priority

normal

Severity

minor

Reproducibility

always

Status

closed

Resolution

no change required

Platform

OS Version

Product Version

Target Version

Fixed in Version

Summary

0002300: Can't read SERV.MAP[x] value

Description

On latest nightly, if I try to read MAPx values from .ini it always return "invalid command" and a console error. Any other .ini setting can be read without problems, but not MAPx values

Example:
MAP0 is enabled on sphere.ini, but when I type ".show serv.map0" I got "invalid command" and these console errors (I just typed 1 command and got 3 errors)

22:57:ERROR:Unsupported Map 0
22:57:ERROR:Unsupported Map 0
22:57:ERROR:Unsupported Map 0
22:57:1:'lol' commands 'show serv.MAP0'=1

The same occour on scripts:

[FUNCTION lol]
FOR 0 5
IF (<SERV.MAP<dLOCAL._FOR>>)
SERV.B lol <dLOCAL._FOR>
ENDIF
ENDFOR

22:59:ERROR:(lol.scp,13)Unsupported Map 0
22:59:ERROR:(lol.scp,13)Can't resolve <SERV.MAP0>
22:59:ERROR:(lol.scp,13)Unsupported Map 1
22:59:ERROR:(lol.scp,13)Can't resolve <SERV.MAP1>
22:59:ERROR:(lol.scp,13)Unsupported Map 2
22:59:ERROR:(lol.scp,13)Can't resolve <SERV.MAP2>
22:59:ERROR:(lol.scp,13)Unsupported Map 3
22:59:ERROR:(lol.scp,13)Can't resolve <SERV.MAP3>
22:59:ERROR:(lol.scp,13)Unsupported Map 4
22:59:ERROR:(lol.scp,13)Can't resolve <SERV.MAP4>
22:59:ERROR:(lol.scp,13)Unsupported Map 5
22:59:ERROR:(lol.scp,13)Can't resolve <SERV.MAP5>

Tags

No tags attached.

Nightly Version

Automated (specify build number)

Experimental Flags

None

Option Flags

None

Internal Build Number

1834

Attached Files

Relationships

Notes
(0002019) XuN (developer) 29-03-14 15:43	AFAIR, you typed it wrong: <serv.map.<dlocal._for>

(0002021) Ben (manager) 29-03-14 16:13	Although not documented, <serv.MAPx...> and <serv.MAP.x...> are both valid syntax for the same command, but SERV.MAPX is not a command on it's own, it must be followed by .ALLSECTORS or .SECTOR.x.command The MAPx ini settings are not readable in scripts.

Issue History
Date Modified	Username	Field	Change
29-03-14 03:09	Coruja	New Issue
29-03-14 15:43	XuN	Note Added: 0002019
29-03-14 16:13	Ben	Note Added: 0002021
29-03-14 16:13	Ben	Status	new => closed
29-03-14 16:13	Ben	Assigned To	=> Ben
29-03-14 16:13	Ben	Resolution	open => no change required