Jump to content

stanhope

Member
  • Content Count

    1194
  • Joined

  • Last visited

  • Medals

Posts posted by stanhope


  1. You wanted a way to disable battleye kicking/banning/reporting/whatever based on script restrictions.  Literally the only way to disable that is to remove scripts.txt.  If you want battleye not to kick/ban/report/whatever players for the new script restrictions you'll need to figure out which rule in scripts.txt is kicking/banning/reporting/whatever is causing this and tweaking this rule. 

    • Like 1

  2. if the !workshop folder can't be found in the arma root directory it doesn't exist.  You can always write up a little script to make something like that yourself, I've done it before to take a launcher html export, parse that, subscribe to the mods, create symlinks and generate a mod line.  If I had written it to a somewhat decent quality of code I'd have published it but it's absolute garbage at the moment, it did work though


  3. Let us know:

    player addEventHandler ["FiredMan", {
    	_this spawn {
    		params ["_unit", "_weapon", "_muzzle", "_mode", "_ammo", "_magazine", "_projectile", "_vehicle"];
    		systemchat format ["Player velocity: %1", speed _unit];
          	while {alive _projectile} do {
            	systemchat format ["Bullet velocity: %1", speed _projectile];
              	sleep 0.5;
            };
    	};
    }];

    (untested and written while half asleep so there may be syntax errors)


  4. 1 hour ago, Pagoda.br said:

    This is an Arma 3 problem?

    Well no, you just said yourself that it's a MySql extDB3 problem. 

     

    As for how to fix it: this command might help.  If it doesn't change the code of your mission to not persist player names and instead persist UIDs (or escape certain character from names when persisting).  Or alternatively don't allow people with special characters in their name on your server.

    • Like 1
×