Better Esseker params, DMS_DEBUG explanation

This commit is contained in:
eraser1 2015-09-13 19:50:34 -05:00
parent af225038af
commit 6cc02bfb89
2 changed files with 3 additions and 2 deletions

View File

@ -5,7 +5,8 @@
Created by eraser1
*/
// If you're gonna make any changes to DMS functions and/or create any new missions, it's a good idea to enable this :)
// Enables debug logging in DMS functions. This will also make missions spawn and timeout more quickly (for testing purposes).
// Disable this on live servers, unless you know what you're doing.
DMS_DEBUG = false;

View File

@ -25,7 +25,7 @@ switch (toLower worldName) do
{
case "altis" : { _safePosParams = [[16000,16000],0,16000,_nearestObjectMinDistance,0,_maxTerrainGradient,0,DMS_findSafePosBlacklist]; }; //[16000,16000] w/ radius of 16000 works well for Altis
case "bornholm" : { _safePosParams = [[11264,11264],0,12000,_nearestObjectMinDistance,0,_maxTerrainGradient,0,DMS_findSafePosBlacklist]; }; // Thanks to thirdhero for testing this info
case "esseker" : { _safePosParams = [[6144,6144],0,6500,_nearestObjectMinDistance,0,_maxTerrainGradient,0,DMS_findSafePosBlacklist]; }; // Thanks to Flowrider for this info
case "esseker" : { _safePosParams = [[6276.77,6352.98,0],0,5000,_nearestObjectMinDistance,0,_maxTerrainGradient,0,DMS_findSafePosBlacklist]; }; // Thanks to Flowrider for this info
case "tavi" : { _safePosParams = [[12800,12800],0,12800,_nearestObjectMinDistance,0,_maxTerrainGradient,0,DMS_findSafePosBlacklist]; }; // Thanks to JamieKG for this info
default { _safePosParams = [[],0,-1,_nearestObjectMinDistance,0,_maxTerrainGradient,0,DMS_findSafePosBlacklist]; };
};