kylania

Password your server. Or use Battleye to whitelist. Both are much better ideas than an SQF mission based whitelist. Your code is backwards though, just leave it as austin medic had it: playerwhitelist = ["123456","1234567","12345678"]; // This checks to see if the steamID of the player (getplayerUID player) is in the playerwhitelist array. if(getplayerUID player in playerwhitelist) then { // Friendly code here, you match. hint format["Welcome to the server %1!", name player]; } else { // Unfriendly code here, you don't match, so kick them here or something. hint format["You're not welcome here you should know, %1!", name player]; };

Should be able to detect a hit to the head and randomly disableTIEquipment or disableNVGEquipment based on that to fake it though.

There shouldn't be anything hard coded into this system. Defaults sure, but no hard limits. Let the mission makers decide bleed time and everything else with the system, or else it's just completely redundant and will be replaced by a player system that does allow that sort of thing.

Based on the documentation it seems that you can use this to toggle the 3D icon visibility: ["taskID", false] call BIS_fnc_taskSetAlwaysVisible; // turn off, use true to turn on. In a mission where the player is supposed to be lost the mission maker probably shouldn't create task destination markers at all in the first place. Map markers make sense as someone can open a map and say 'Hey, a port, lets go there!" and those automatically "disappear" should the player lose a map.

I think that's the new LeftControl+RightClick+W "Look Over Everything" stance. :P

It's $28. Everyone has wasted more than $28 worth of time complaining about it. Just get the DLC or don't. CoD is $60, Battlefield 1 is $80, Overwatch is $60, Doom is $60, DaZ is $35, Killing Floor 2 is $20, GTA V is $60. $28 is the paper mache of paywalls.

The current Release Candidate branch was recently upgraded. Dev branch continues to be updated daily however. Both have all the content, Dev will just have more bug fixes.

If you have no ItemMap you can't see the map, nor any markers, anyway.

It's in game.. taunting us, constantly... :mellow:

Umm.. not really, if you're comfortable with triggers, by all means continue to use them. There's the endMission gotcha to think about, but otherwise modules should be OK now.

Ok, replace failMission with _task = ["task1", "FAILED"] spawn BIS_fnc_taskSetState;

https://forums.bistudio.com/topic/191085-number-of-civs-killed-5-end-mission This doesn't do the did the player do it part, but shows the count part. :) EH instead of trigger.

Mynock wrote a script to do just that. There's a strange bounce as it settles though.

<marker name='markerName'>link title here</marker> You'd embed that in your task description. Clicking on the link title will center the map over the marker you had, even if it's an Empty marker.

You can script a solution. Put down an ammo box, addAction it and have that spawn the weapon you wanted to recover or whatever.

Woo! From today's dev branch changelog:

I was working on a mission spawn script the other day and instead of using a Radio Alpha trigger, I decided to get diabolical and instead ran the script from an onHit eventHandler on some poor AI. It was super fun! Time to test? BANG! Splat! Spawn! Time to test again? BANG! Splat! Spawn! That's when I started hitting multiple parts and ended up spawning multiple things in the same location and blew my base up... oops. What I'm trying to say is, be prepared for multiple returns. :)

Ha! You're doing pretty well then. :)

Is your initserver.sqf file listed in Windows explorer as an "SQF File" or a "Text Document"?

I saw that stuff the other night looking at someone's issue. If you have Playable units on the map you're locked into Multiplayer tags and can't change it before or after publish.

While that's true, please bear in mind this note from the Biki with regards to BIS_fnc_endMission:

Do you see the same behavior in the Editor with no mods?

At least with Friday's Dev Build you could still open it via scripting. We just want the addAction back on the pilot so we don't have to. No extra functionality, no integration with the ViV system, just let the pilot (and scripts!) animate the ramp opening and closing as it was when we first saw the vehicle and as it is with the infantry version.

When you say "enemy towards everyone" do you mean "enemy towards BLUFOR and INDEPENDENT"? Because that's simple. If you want them enemy against OPFOR as well, then you're designing a poor mission. :) To make only Syndikat units hostile to B and I you need to place down a higher ranked OPFOR unit first, then group the Syndikat to them. Set the OPFOR unit to 0% Probability of Presence by expanding Object: Presence in it's attributes and setting the bar far left. That unit won't actually show up in game but will make the group they were leader of count as OPFOR. You'll see them outlined in red in the editor if you did it correctly. Actually, looks like in Eden you can delete the OPFOR unit and they remain OPFOR. Hmm. Probably safest to leave them there as 0% though.

Neat idea, but Facebook seems like the worst place to do this kind of thing. The lack of proper text formatting is a huge minus. Code examples look horrible unformatted. Posts are difficult to find (no table of contents or cross links) and squished in a tiny column in the middle of utter distractions. Even maximizing the browser to 1920x1200 still keeps the actual text a mere 500 pixels across. Facebook just isn't good at presenting information for reference, especially not when code will be involved. Instead of simple timeline posts you might try using Facebook Notes. There's limited formatting available, critically the ability to have highlighted code sections, and while it's painful to use it lets you create a post that looks like this instead of this.