Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[kkl]

According to this Core Commands wiki, I should be able to change zones using the 10011 MCC_SET_ZONE command:

MC18.EXE /MCC 10011, n

I have only two zones, Family Rm and Theater.  No matter what integer I use, the zone is set only to Family Rm.  So, 0, 1, 2,...10, all set the zone to Family Rm.   Same thing happens with the -1 or -2 options.  I added a 3rd zone just for testing.  Same behavior, only result is Family Rm.

Is this a bug?

[Matt]

Remove the space after the comma:
MC18.exe /MCC 10011,-1

Or put the parameter in quotes:
MC18.exe /MCC "10011, -1"

[kkl]

Thanks very much for the quick response.  That was the trick.

The documentation definitely has a space:

"MC<version>.exe /MCC <command number>, <parameter>"
"MC16.exe /MCC 10000, 0"

So, I'd suggest it be corrected.

[MrC]

That was my fault - I will fix it in the morning.

[Matt]

I don't see any reason to be so picky.  It was just an unintended consequence of the revised command line parser.

In the next build:
Changed: MC18.exe /MCC allows a space after the comma (ie. "MC18.exe /MCC 10011, -1").

[MrC]

I thought it used to work that way, but when the OP reported the problem, I starting thinking Twilight Zone.