Base Building DayZ 1.2 Released
- Thread starter daimyo21
- Start date
i'
I'm using reality build, i try to add the tent fix, i think i doesn't need the first fix, not? in the second fix, for remove problems. I have problems to implement it, because my code is different and does not affect me when applying:
my code:
And I dont understand why my code to send data to DB is diferent:
only when I tried to change PVDZ_obj_Publish instead of dayzPublishObj as was originally in my default files, began recording in the database, may fail something in the code that I modified. any ideas? thanks in advance
I'm using reality build, i try to add the tent fix, i think i doesn't need the first fix, not? in the second fix, for remove problems. I have problems to implement it, because my code is different and does not affect me when applying:
my code:
Code:
_object_killed = {
_object setDamage 1;
call _object_damage;
};And I dont understand why my code to send data to DB is diferent:
Code:
_object setVariable ["characterID",dayz_characterID,true];
PVDZ_obj_Publish = [dayz_characterID,_object,[_dir,_location],_classname];
publicVariableServer "PVDZ_obj_Publish";
} else {cutText ["You need the EXACT amount of whatever you are trying to build without extras.", "PLAIN DOWN"];call _funcExitScript;};only when I tried to change PVDZ_obj_Publish instead of dayzPublishObj as was originally in my default files, began recording in the database, may fail something in the code that I modified. any ideas? thanks in advance
Hi I haven't posted here in a while. Just wondered if some one could explain how the key panel for opening a base is supposed to work? What does it open? Does it need linking with something? Can you set a password?
Also players who have built something can at first remove it straight away and get refunded for the buildable beind deconstructed. But I think after they die or a server restart not entirely sure it forgets they built it and makes them "attempt" to deconstruct it as if they didn't even build it.
Any one who has any idea what I'm on about help would be awesome! x)
Also players who have built something can at first remove it straight away and get refunded for the buildable beind deconstructed. But I think after they die or a server restart not entirely sure it forgets they built it and makes them "attempt" to deconstruct it as if they didn't even build it.
Any one who has any idea what I'm on about help would be awesome! x)
Key panels open 'gates', the gates are the concrete walls. Those thin grey ones that are like the second or third item in the build list. They will toggle all of them within a 300m radius I believe it is. You can't change the code, without Kikyou's improvements, though that's going to change soon.
The removal script currently checks the 'owner_id' of the deployable item, against the 'character_ID' of the player trying to remove it. Sadly, once you die, you get a new character_ID. It's not a great work around, but what you can do is put an SQL script in place to update the deployable items of dead players before each server restart.
Code:
CREATE EVENT `updateDeployableOwners` ON SCHEDULE EVERY 6 HOUR STARTS '2013-09-02 05:56:00' ON COMPLETION NOT PRESERVE ENABLE COMMENT 'Update deployable owner if they died' DO UPDATE instance_deployable d LEFT JOIN (
SELECT DISTINCT d.owner_id, s.unique_id
FROM instance_deployable d
LEFT JOIN survivor s ON s.id = d.owner_id
WHERE s.is_dead =1
) AS dead ON dead.owner_id = d.owner_id
LEFT JOIN survivor live ON live.unique_id = dead.unique_id
SET d.owner_id = live.id WHERE live.is_dead =0Adjust the times in that to suit your restart schedule and then run it as an SQL Query.
This too will soon become a thing of the past. Watch this space haha.
If you had to change that variable, you should probably use the 1.8 fix in my sig. It has all the updated public variables. I wasn't sure if Overwatch used 1.8 yet or not.
1.7
It must be 1.7.7.1 or 1.8+ to use those variables. Everything before 1.7.7.1 used the old ones.
How does the key panel work then? Are you saying if I built one by some one elses base it would just open all their gates? Or if I build a key panel will it only open gates that I've built?
Yeah, sadly they aren't the most secure really because if you did build one near somebody else's gate, you could open their gates. Though there can only be two key panels within a 300 meter radius of each other, so if they were smart they would already have built one on the inside and one on the outside meaning nobody else could come along and build one near their stuff.
Just add !"inmotion" to the first line of your setvariable.txt file.
The Server Guy
New Member
I have working overwatch 2.5 with basebuilding files msg if you want them
For now, open player_remove and after
Add
Should remove the action from their screen. Since the fn_selfActions is already set not to show the option if people are removing an item that should already prevent it coming back.
Code:
disableserialization;
Code:
player removeAction s_player_deleteBuild;
s_player_deleteBuild = -1;
player removeAction s_player_deleteCamoNet;
s_player_deleteCamoNet = -1;