runaway while blocked from collar

[Medea-Destiny]

If wearer is blocked from their own collar, a runaway chat command will not be sent to userCommand. We should have an exception to this for the runaway command, as the whole point of runaway is to clear auth lists. We have disable runaway to handle this situation anyway.

[AkashaImon]

ive been trying to use the runaway command because i no longer talk to the person but im restricted from everything. i cant even update the collar. How do i fix this?

[Pingout]

@AkashaImon turn off RLV in the viewer then reset the collar scripts

[NikkiLacrima]

"Restricted from everything" I am not sure what is restricted, is it RLV restrictions blocking the use of local chat ? Or has runaway been disabled ?

If it is RLV restrictions then the menu runaway command still works.

If wearer has been put on the blocked list, then the chat command prefix runaway works in the latest #1010 patch for 8.3 development but it does not work in 8.2.3 , so this issue is fixed.

If runaway has been disabled, well the point is that the wearer not should be able to runaway so making some exception defeats the runaway disable functionality. In this case a reset with RLV disabled as Ping suggested.

Tech details:
oc_api does the test
else if(iNum >= CMD_OWNER && iNum <= CMD_NOACCESS) UserCommand(iNum, sStr, kID);
to pass commands to UserCommand this allows CMD_BLOCKED through to UserCommand.

In other parts of the code, like in oc_core the test is
if(iNum >= CMD_OWNER && iNum <= CMD_EVERYONE) UserCommand(iNum, sStr, kID); blocking CMD_BLOCKED from UserCommand.