Search results

still looking into the spawn bug. tested the relog bug and i can not duplicate it is there any more information you can give me.

correct it now adds a option to the scroll menu if that is active you can teleport on top of buildings they need to be on there own lines, for some reason github messes with the formatting of the readme file that is a variable name it really does not matter what it is named

Please review the install instructions inside README lines 31 to 36

what map are y'all installing this on?

looking into it i will keep you updated

you spawned a s a bird correct?

found your problem. if ((getPlayerUID player) in ["Merg","Merg"]) then {please review the install instructions in the readme

give this a try

up load your mission pbo

fixed skin change removing menu. to update replace current skins folder with the new one

change the code in Activate.sqf to waituntil {!isnull (finddisplay 46)}; sleep 60; if ((getPlayerUID player) in ["#######","#######"]) then { player addaction [("<t color=""#0074E8"">" + ("Tools Menu") +"</t>"),"admintools\Eexcute.sqf","",5,false,true,"",""]; }...

you failed to follow my install instructions in the readme find this code if (!isDedicated) then { // If mission is loaded by a player execute the player monitor 0 fadeSound 0; 0 cutText [(localize "STR_AUTHENTICATING"), "BLACK FADED", 60]; _id = player addEventHandler ["Respawn", {_id = []...

i found this bug myself approx 1 hr ago. i will work on a fix tomorrow

as i said before i have no idea YET F5, F6, user action #19, and user action #20 are no longer valid. try this in Activate.sqf change the code to waituntil {!isnull (finddisplay 46)}; player addaction [("<t color=""#0074E8"">" + ("Tools Menu")...

relog

scroll your mouse wheel

that code was taken from the scripts.txt file you uploaded, as the code above is script restriction #18 and the value is set to 1 there is no possable way you can be KICKED for #18

this is the restriction for #18 1 createUnit !"\"createUnit\"," !"BIS_MPF_logic = BIS_MPF_dummygroup createUnit [" !"_newUnit = _group createUnit [_class,dayz_spawnPos,[],0,\"NONE\"]" the "1" at the very start of the line means log to file do not kick, therefore you can not be getting kicked...

if i do not know what the problem is how can i fix it?

are you sure there script restrictions and not createvehicle, remoteexec, publicvariable...