OK - now I've got what You meant. But how about that below?
Quote:
Originally Posted by BAILOPAN
If there was a radar_disable option for the FFA section (0=none, 1=scramble, 2=client disable), with 1 being the default, I'd say it's okay. But changing client settings by default is bad.
|
You mean - if I'll add the option "radar_disable" in FFA section with default 1=scramble action, that stuff with hideradar can stay in the code (for the option 2=client disable)? If some server admin will decide to use that option - the clients of his server will have the same issues, so it will be bad anyway...
About that scramble - maybe there is a way to "clean" the radar - send to the user the info (as radar message) like "the teamnates are dead" (or something like that) - so the radar will show nothing. As I described it few posts before and the user was complaining, too, the current method (in the original csdm_ffa plugin) is not satisfacting, so we need to find some better solution.
The Fullpack of podbot mm
V3B22 - 24 apr 2012!!! is available
here.
The All-In-One 3.2a package - 02 jun 2013 (
AMX X 1.8.2 [with ATAC 3.0.1b , CSDM2.1.3c beta, CM OE 0.6.5, podbot mm V3B22c and mm 1.20) is available
here.
The newest Beta V3B23a (rel. 28 august 2018!!!) is available
here.