BigEgg

They wouldn't be able to build another plot and they wouldn't be able to build above the height limit that you set. Everything that was already built would remain at that height, but if they had for example a floor above your height limit, they would no longer be able to build on that floor, but that floor will still remain there as long as it is maintained.

I don't know if this could be causing the problem, but do you have this in as well?
 
 
I apparently forgot to add this to the original post sometime back, but it prevents you from raising it above the height while building.
 

This is the correct format (example pulled from my server):
BlacklistedBuildings = [ ["Fire Station", "Land_a_stationhouse", 250], ["General Store", "Land_A_GeneralStore_01", 250], ["Hospital", "Land_A_Hospital", 250], ["Fuel Pump", "Land_A_FuelStation_Feed", 250], ["Fuel Station", "Land_fuelStation_army", 250], ["Fuel Station", "Land_fuelstation", 250], ["Fuel Pump", "Land_Ind_FuelStation_Feed_EP1", 250], ["Fuel Pump", "Land_ibr_FuelStation_Feed", 250], ["Fuel Pump", "Land_fuelStation_w", 250] ];  

If you'd like, I could get in contact with you sometime tomorrow and take a look, as something simple like this should not be causing these problems.

This would be an install issue if you are being able to go 60m up, as countless people have installed this. Please be sure you have done everything correctly.

I would double check, as those options are strictly controlled by fn_selfActions and should not be effected by these additions.

And you are positive that you haven't changed anything in fn_selfActions? No matter what you should be getting the options, so this is clearly an issue with it.

Hey Lance, I will have this updated in a couple hours when I am able to get on my P.C. Thanks for reminding me!

Yes two hour restarts.
 
Fortune is the text document that you paste message into that you want displayed on your server.

This is what I just threw together, probably more inefficient ways possible, but I am not going to go through testing for this:
 
In mission_init.sqf find the marker loop and replace with this:
while {_running} do { _type = (wai_mission_data select _mission) select 1; if (isNil "_claimedby") then { _dis = 1000; { _dispos = _x distance _position; if (_dispos < 1000 && _dispos < _dis) then { _claimedby = name _x; _dis = _dispos; }; } count playableUnits; }; _marker = createMarker [_type + str(_mission), _position]; _marker setMarkerColor _color; _marker setMarkerShape "ELLIPSE"; _marker setMarkerBrush "Solid"; _marker setMarkerSize [300,300]; _marker setMarkerText _name + if (!isNil "_claimedby") then {"Claimed by: " + _claimedby} else {""}; _dot = createMarker [_type + str(_mission) + "dot", _position]; _dot setMarkerColor "ColorBlack"; _dot setMarkerType "mil_dot"; _dot setMarkerText _name + if (!isNil "_claimedby") then {"Claimed by: " + _claimedby} else {""}; sleep 1; deleteMarker _marker; deleteMarker _dot; _running = (typeName (wai_mission_data select _mission) == "ARRAY"); };  
This should get the closest player within 1000 meters of the mission and change the name to show he has claimed it. This could be quite intensive, so be cautious if you wish to increase the distance. Let me know if it works as I haven't tested.

This tool: http://bem.themeq.xyz/ - formats it correctly and so does the other one, however, I don't believe it is necessary in some cases or at all. However, that tool has never caused me in formatting issues.

If you want me to put it in for you let me know.

Here, you are setting _isrunner to a number. You are getting the variable in a true/false manner though, which means you want to set it as true.
 
I have corrected your code below:
_rnd = random 1; _isrunner = if (_rnd > .985) then {true} else {false}; _agent setVariable["isRunner", _isrunner, true]; _isrunner = _agent getVariable["isRunner", false]; if (_isrunner) then {diag_log "A Zombie is a Runner";};  

You also do not need to have:
if (_isrunner = true) then { This is accomplished by simply doing:
if (_isrunner) then {  
It would be the same as saying:
if (true == true) then {  
Also, when determining whether something is equal to something, two "=" signs are used.
 
Example:
if (1 == 1) then {systemChat "Correct syntax";};  
You are getting the missing ) because of the above mistakes.

It appears you are not making it visible to all machines. Try this:
 
_agent setVariable ["isRunner", _isrunner, true];

I am assuming slower because they use callExtension.

Hey Lance, I will have this updated in a couple hours when I am able to get on my P.C. Thanks for reminding me!

Restrict Building is part of Epoch 1.0.7.1 now.
 
While there may be some extra features built in to 1.0.6.1 that restrict building, I needed more options.
 
What this does:
Allows server owners to restrict entire zones of the map (for example - no building within 1,000 meters of Balota). Allows server owners to restrict building near certain buildings, and allows them to define the distance and name of each building they are restricting.  
Step 1:
In your init.sqf find:
// EPOCH CONFIG VARIABLES END // Directly under it, add:
// Restrict building near specific buildings BlacklistedBuildings = [ // ["What text will say", "Class name of building you want to block", Distance around that building to block (radius in meters)] ["Fire Station", "Land_a_stationhouse", 250] ]; // Restrict building near map areas RestrictedBuildingZones = [ // ["What text will say", [Choords of place to block], Distance around that area to block (radius in meters)] ["Balota Airfield", [5158.72, 2518.75, 0], 600] ];  
Step 2:
In your custom compiles.sqf add (NOTE: CHANGE THE FILE PATH TO FIT YOUR NEEDS):
dze_buildChecks = compile preprocessFileLineNumbers "FILE\PATH\HERE\dze_buildChecks.sqf"; into the if (!isDedicated) code block. Example:
if (!isDedicated) then { dze_buildChecks = compile preprocessFileLineNumbers "FILE\PATH\HERE\dze_buildChecks.sqf"; };  
Step 3:
Create an SQF file, in the path you have designated above, and name it dze_buildChecks.sqf.
 
Step 4:
Paste the following code into dze_buildChecks.sqf and save the file.
 
Done!
 
Be sure to configure the settings in your init.sqf to your liking.

I mean, that would be weird. @Anhor, could you also post your dze_buildChecks.sqf?
 
@juandayz, here is the code that sets dayz_actioninprogress to false.
if (_cancel) exitWith { dayz_actionInProgress = false; _reason call dayz_rollingMessages; [false, _isPole]; }; All of the restrictions that I added in this script go through this block of code if they are met. 

If there are no errors then I honestly wouldn't know where to begin. I am not having this issue, nor is anyone else. Would you mind posting your client and server rpt logs (be sure to use spoilers)?

And you are positive that you haven't changed anything in fn_selfActions? No matter what you should be getting the options, so this is clearly an issue with it.

I would double check, as those options are strictly controlled by fn_selfActions and should not be effected by these additions.

This would be an install issue if you are being able to go 60m up, as countless people have installed this. Please be sure you have done everything correctly.

If you'd like, I could get in contact with you sometime tomorrow and take a look, as something simple like this should not be causing these problems.

This is the correct format (example pulled from my server):
BlacklistedBuildings = [ ["Fire Station", "Land_a_stationhouse", 250], ["General Store", "Land_A_GeneralStore_01", 250], ["Hospital", "Land_A_Hospital", 250], ["Fuel Pump", "Land_A_FuelStation_Feed", 250], ["Fuel Station", "Land_fuelStation_army", 250], ["Fuel Station", "Land_fuelstation", 250], ["Fuel Pump", "Land_Ind_FuelStation_Feed_EP1", 250], ["Fuel Pump", "Land_ibr_FuelStation_Feed", 250], ["Fuel Pump", "Land_fuelStation_w", 250] ];