janus0104

Hey there, just came to express that I'm hoping you'll include the latest iteration of PLP Containers in your next version. Having the cake and eating it, too, without additional file size ;) Cheers and keep up the good work!

While true, remember that it is impossible to cagetorize everything. Some stuff simply needs to be put in prose writing. Think of issue trackers. There are like 30 fields that you can sort and filter by. But when you do it for units, all it does is filter out units you could actually be interested in but are slightly outside your search scope.

One simple change request: For unit tags, have it replace "[[" by "[", and "]]" by "]". Double brackets just look silly as in the creator of the unit didn't know whether the system would automatically add brackets or not.

I see your point in terms of being easier to do. A full port would be welcome though without having to use CUP. As for "CUP is adding alot of new content as well as porting all of the A2 default content.", you are entitled to your opinion as such, but don't jump to the conclusion that surely everyone must agree with it. Some people just don't like CUP. Or would like to only use one element of CUP, but that's impossible. Or simply have tested the various things CUP currently has to offer and have walked away with an opinion of "maybe in a year or two, when stuff works". But that doesn't really have anything to do with this mod. The bottom line is: If this mod were alternatively/optionally available as a stand-alone, it would have more users.

Crewmen: Always go for Vanilla, if mission makers need specific crewmen they will place empty vehicles and assign specific crewmen anyways. Dependencies that might be overlooked: Uh, please elaborate what you mean?

REQUIREMENTS: - CUP soldiers and weapons. You MUST have CUP to use this pack! You are using CUP aren't you? ;) No, I am not using CUP for a number of valid reasons. This dependency to CUP a.) seems arbitrary / unnecessary b.) means hundreds of players who would otherwise play this mod are not going to. You are of course free to make your mods however you want :) Just giving you honest feedback on that end.

- Localization. Can we please have the option of entering fields with multiple values specific for language? Say, a short description in language 1 and one in language 2, same for the full bio, same for website link for those who offer localized websites, etc. Most clans who are not from an English-speaking country may for example have one text in their native language and one in English, the default language being a.) the language set by the user if one is logged in or b.) if not logged in, or not specified, go by browser location I guess? or c.) use the language the unit states as their "operative language", i.e. the language spoken while playing and thus is required for participation. This may also help with international cooperation. "Hey, we're a french unit, but we'd be happy to try playing against/with units from elsewhere aslong as we can find a common language to speak (when in doubt, English)" etc.

- 100+ as the largest unit size category seems unwise in terms of scaling. Maybe 500+ as the largest and then some more steps between 100 and 500? - Identity theft, copyright infringement and troll content seem rampant. I had to report a hand full already, no response or action so far.

Was this in 1.3 aswell, or is this a new issue? The aft starboard elevator has a spot where you get stuck walking over it and eventually... die :(

Armaholic page lists what jets are recommended. Personally, I recommend John Spartan's F/A-18E / F. As for A-10, those are not carrier capable in real life :P As for random exploding, try moving the nimitz around a bit in the editor, it seems to help.

Any chance for a fox-logo beret (infamous salute scene)?

Solved. We had a different mod.cpp, which somehow is relevant now?! If anyone runs into similar issues, watch out for that ;)

Our dedicated servers no longer start up properly with newest CBA. No other mods running. Errors like 21:14:02 NetServer::finishDestroyPlayer(359706660): DESTROY immediately after CREATE, both cancelled when trying to connect. Can't gracefully shut it down, have to kill the arma3server process. Works fine without CBA. Verify Signatures off. Persistent over multiple physical machines.

Same thing here, please keep the two as separate packages.

Very much so, I believe. What map(s) were you trying it on?

Hmm... I'll test some more then.

There seems to be an issue with the newest version's hitboxes. Just updated, using TFA_black as uniform and TFA_PlateCarrier_black, we get only one arm as hitbox, the rest doesn't register. Which bugs out CSE's Combat Medical System :) Not sure if it's an issue with the armor being too strong or the hitboxes being weird but I tested with and without TFA, proper hit zones and damage in vanilla, no damage other than right arm with TFA.

If you mean full heal (using the first aid): That is intentional, you simply can't do some procedures on yourself. Same for IVs I think.

Noone's going to maintain it, it's a one-time event. Like Rolling Thunder... And we can't expect 100 players to download 6 GB for one evening of ArmA 3. Don't ask me why they don't use AiA TP, but that's hardly something I can change :P My community does use AiA TP and we enjoy it greatly, but we can't force our taste on guests for a single event.

Is there a list somewhere which pbos which map needs? Or a clever way to figure out? We're about to host a larger event with multiple communities and need to reduce the size of files everyone has to download.

Sometimes, that still happens. The fun of ArmA, fixing one thing breaks another. But we're hopeful we can push something within the next 24 hours.

Hotfix? Is something not working there due to a technical problem? The config on the CSE wiki has been updated, you'll have to update your config file accordingly ;) It's not really something we have a seperate download for with each version update since the PBO itself doesn't change.

Yea, probably. But can't give an ETA :) Unlikely, there's just too much overlap of functionality, code difference, different priorities and tastes. I'd rather there be both and players have a choice of taste.

I think that's just the root class for the darter battery, iirc, so other types of batteries can in the future be added with the same root. So... no use for that empty class there yet :)

Yes, it can, and will be over the next few days :) Basically, we don't want to double our efforts there, so we'll update it with the newest information for the upcoming patch once everything there is final to be handed out to our testers. For your most urgent needs: - Advanced Wounds is unrelated to Basic Revive. The first makes it so bandaged wounds can reopen, the latter lets you set a delayed death, i.e. if you WOULD die, you won't die until the configured amount of seconds elapses, giving medics that much more time to save you. Some things are not covered by it, e.g. heli crashes (noone could get to you with it being on fire, so we spare you the wait) or drowning. - Set medics: Say you have 5 units and you have set their names to be s1, s2, s3, s4, s5. You can then just add e.g. "s1,s2" without the brackets into the Set Medics Class module's line (don't remember how it's phrased exactly, but with label and tooltip you should find what I mean) and it will make those slots into medics no matter how often they have to reconnect. Any other questions that make it impossible for you to properly set up a mission, feel free to ask. The wiki we'll update as soon as possible :) Just not tonight.