Page 1 of 1

Some semiadmins commands no longer working with ETPro 3.2.1

Posted: Wed Aug 24, 2005 12:44 am
by Bombosman
We've noticed that some semiadmin commands no longer work for ETPro 3.2.1 (while others still do their job). For instance, "timelimit" gives the following log (and does nothing):

Code: Select all

...
etpro semiadmin: 1 *** (level 2) command [timelimit 15:00]
unknown cmd in line '20'
...
Another buggy command is "nextmap" which actually only makes somekind of "match_restart" (the log shows no relevant information).

I guess it might be a problem with the "new custom semiadmin commands support" (what are the commands defined by default?).
________
CHRYSLER TOWN AND COUNTRY (PRE-1990) SPECIFICATIONS

Posted: Wed Aug 24, 2005 2:16 am
by bani
the new way semiadmin works is that when a semiadmin executes command bla, etpro checks for a file bla.cfg to execute, then checks for a cvar called bla to vstr, then if neither of these exist it sends the command through to the console.

timelimit and nextmap are cvars :P so you're getting tripped up on the second rule. i could modify the second rule so it looks for a cvar called bla.cvar instead.

Posted: Wed Aug 24, 2005 7:08 am
by Bombosman
Yeah, I got the the feeling of missing something and many thanks for clarifying out this point. I hope you can make a clean solution for the "timelimit situation" (shared with any other request that needs to bypass arguments, if I understood well the problem).
________
Extreme Q

Re: Some semiadmins commands no longer working with ETPro 3.

Posted: Tue Sep 27, 2005 7:47 am
by redshadow
Bombosman wrote:We've noticed that some semiadmin commands no longer work for ETPro 3.2.1 (while others still do their job). For instance, "timelimit" gives the following log (and does nothing):

Code: Select all

...
etpro semiadmin: 1 *** (level 2) command [timelimit 15:00]
unknown cmd in line '20'
...
Another buggy command is "nextmap" which actually only makes somekind of "match_restart" (the log shows no relevant information).

I guess it might be a problem with the "new custom semiadmin commands support" (what are the commands defined by default?).

I gotted same problem, but only sometime :o

Posted: Wed Sep 28, 2005 4:37 am
by bani
this will be fixed in the next version.