Solidsnacks

How exactly are you spawning/ respawning them? If you have an example I might be able to help.

Alright. Let's cut the shit and keep this simple. 1. Open the editor and choose a map of your choice. 2. Place a marker. Right-click the marker and select "Attributes" . In the following menu type "respawn_West" (without the quotation marks) in the "Variable Name" field. 3. Place a "BLUFOR" unit. It will be playable by default, but you can also go into its attributes and ensure that it is playable under the "Object: Control" tab. (You can select any unit type you like, but it's simpler to select from the "Men" category. 4. Paste the following into your Description.ext. 5. Paste the following into a file named initPlayerLocal.sqf 6. Test the mission by hosting a local server (LAN). This will give you a Multiplayer Respawn menu with four "Roles", and a variety of "Loadouts". You can go into the "Description.ext" and tinker around with the various "Loadouts" and add or remove them via the "initPlayerLocal.sqf" file. Like some have mentioned; You will need to do your homework if you want to get the results you're looking for. I recommend reading everything you can on the following links and try to understand how they are connected to each other. Arma 3 Respawn Description.ext

Nice catch @Larrow! Another thing I’ve noticed is the trigger attributes can be modified and saved in the mission.sqm. Then you can load/ save, and preview the mission without the attributes changing, but the moment you start changing any of the trigger properties in the editor it will add the call {attribute}. Seeing how I’m only using a small number of these—-and don’t mind manually changing them in the editor—-I consider my problem solved. For the sake of anyone else that might struggle with something similar; can you suggest somewhere to start looking to learn how to restrict that behavior?

Hey all. I took a couple of weeks away to rethink what was going on and decided to look in the mission.sqm to see if there was anything different about the triggers and their statements. I found this I decided to compare it to the original mission.sqm and found this. The interesting part is the changes in the "condition" and "onActivation" fields. I went into the mission.sqm and manually changed them to match the original and got the desired behavior from my switch statement. Once again, the trigger is directly copied from the original mission so I get the feeling this isn't how it's supposed to work. When I load the mission it changes the trigger "cond." and "onAct.". Does anyone know why this is happening and/or how to prevent it?

Thanks everyone for chiming in. Much respect to all of you. @killzone_kid I get what you mean by “select 1” returns the “on activation” statement. The part that’s messing me up is that I have the triggers configured identically to the ones in the original escape scenario so I’m really at a loss for why it wouldn’t give me the same output as the original. The original triggers simply have MRAP, APC etc (no quotes “ “ or anything) in the “on act.” block. So I’m not sure if you meant something else in your last sentence. @dedmen I had a friend tell me the same thing so I’ll have to see if something pops up in the logs ‘cause it’s not throwing any errors or anything that I can see in the rpt—if that’s even a thing. Thanks again, all! I’ll update when I get home and can check it out.

Right. I should have mentioned that I use the cases in the trigger statements from empty detector triggers in the editor. I’ve reviewed everything and it’s all 1:1. Would anyone like to reproduce this on their end?

I have a switch statement that fails to return any of the cases and instead returns default. I've used different classnames for default and they work successfully but the cases fail to return when called. The script is copied (the entire file TBH) from BI's 'Escape from Malden' initServer.sqf with the only changes being the changes to the classnames the cases reference. My initServer.sqf edit: The original unedited version:

Hi Temppa! I posted on your workshop page but figured I might as well mention it here as well. The ambient sounds are bugged whenever you move away from vegetation. They become mute and the game becomes weirdly silent except for your character movements. I love your maps especially hellannmaa so this is an especial bummer for me. Thanks for what you do!

You have all the medical items in the wrong “field”. They need to go in the “items” section. The “linked items” is for headgear, goggles, attachments etc that have slots in the inventory parsed for them

If you look at the mission in the editor you’ll see there are empty detector triggers located around the map that have Gen_Infantry/ Nato_Infantry in their “text” fields. These need to be placed within your mission for the corresponding code to execute. Also, it would help if you could share the original initserver.sqf that you copied and the one you created for your mission

This is the relevant stuff. The unit is placed in the editor with "US_ARMY_FTL = group this" in its init. Technically, it's alive at mission start. I've considered a switch (true) do alternative to sort it out, but it would seem the base FUNCTIONality has my bases covered, unfortunately it does not I've tried calling it from different events: init.sqf, unit server etc. all with the same result: that the variable US_ARMY_FTL is undefined

So let's take a look. The target in this case is a unit placed in the editor given the name: US_ARMY_FTL. For some wild reason unbeknownst to me, the script seems to think that US_ARMY_FTL is an undefined variable. Can anyone comment on why my logic is wrong? To be clear: the script works if I use missionNamespace, Side, and Group. it DOES NOT work when I try to reference a specific unit.

Thanks for the reply. I mustn't have been clear when I said that the script works fine in the first example. I've gone over the above page you've linked many times and I can't figure out why it can't produce a specific loadout for a specific unit/object as per the function's parameters and posted my example to see if anyone else could spot what I've done wrong or explain why it wouldn't work. Thanks!

As the name implies, I'm asking advice on how to create custom respawn inventories per unit using BIS_fnc_addRespawnInventory. So here's the situation: I have a group placed in the editor, the group is named and each unit belongs to the group and has "US_ARMY_FT = group this" in their inits so they all belong to the same group. Each member is individually named "US_ARMY_FTL, AR etc. So they all have a specific variable name with a similar naming convention. Here's where it gets confusing. I'm able to use BIS_fnc_addRespawnInventory to give the group respawn inventories without a hiccup. The following is what I use for the loadouts. Everything's fine when I use this method, but I wanted to fine tune it so there would be more emphasis on role selection in the lobby and also to force players to use equipment appropriate to their class. So then I came up with this, which is more or less the same as above but references the unit's variable name. Whenever I try this second method it gives me an error saying that "us_army_ftl" is an undefined variable, which is ironic considering that it says nothing about the group I reference for respawn tickets. Additionally, I have other scripts and functions that reference the unit names I've applied and I've received no error messages about them and nothing has been logged in the RPT other than the undefined variable error to indicate anything has gone wrong. It's worth noting that despite the game throwing that specific script error on mission start and it not behaving the way I want it to it still gives me the custom classes that I defined in the Description.ext based on the entries above. So my questions are: How do you make a respawn menu with loadouts custom to the unit/object. Can you do that? Why does the script think my variable is undefined? Thanks in advance!

Good job! I had actually been sifting through a3\ui_f_data\... last night, but was always a hair away from what I was looking for. Once I get some proper examples set up I'll throw them onto here. Seriously, big thanks, Larrow!