Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
OPFOR appears to be located only inside the AO. Since the AO is a BLUFOR defined Area (for that specific mission) wouldn't it make sense to also place some opposite forces outside the AO (patrols and such) - I guess the enemy doesn't care much about ones defined are of operations... :)
Another:
Do you plan to implement the large, fixed wing UAVs? You just implemented the Stomper short ago, is that right?
Bucketsmith hope its allright to abuse this thread to add my suggestions here aswell ;)
I had bleedout time options active for all of 10 minutes then discovered that their addition broke the game so hard I couldn't open the MP host menu so I rolled that back very quickly :)
That was using a BIS suggested script addition though so I'm not sure what went so wrong, hopefully I can find a solution.
I've run out of time to reply further, just wanted to let you know I've read these and I'll get back to you.
Regarding AI revival - currently BIS revive does not support AI either to revive them or have them revive players. The update I pushed yesterday at least makes sure they can respawn properly and places the respawn position closer to the team location. There's room for expansion and I have a few ideas on what to try, but I want to avoid hacking together a solution that is only going to cause compatability issues down the line.
Now that respawn can be disabled the mission should be ACE3 compatible but I don't want to base any mission functionality on other mods as I then need to maintain compatibility with them going forward. More mission ideas are always welcome though regardless, vehicle retrieval sounds like a good one, building a FOB probably doesn't align with the recon nature of the scenario.
Thanks again for the suggestions, I've got some of them on my list to work on soon!
Great, sure would be much appreciated by many Recons!
Concerning the stomper: Last time I wasn't able to turn off the lights and had to shoot them in order to make it stealthy - is that due to the mission or can't it just turn off the lights?
Also - in case you'd implement the fixed wing UAV - how woul'd one connect to them (The stomper need to be hacked first...)?
Released hostages seem a prime target for the enemy, and for my mate and I we tend to be unlucky with those post-captives to die before we get a chance to extract. Or the objectives are laid out in such a way we're forced to rescue him before doing the other objectives.
Another suggestion; Vehicle resupply support drop.
I'm not sure but I believe it's possible(perhaps it was a custom script/mod) to set down something like a container that has refuel, rearm and repair capabilities.
On a side-note; will you be creating your own suggestions thread to maintain a list that everyone can read?
I haven't gotten around to putting up an 'official' suggestion thread - honestly because, while I really appreciate all the suggestions and do often try to work them into the mission, at the end of the day this is a project I do for fun in whatever spare time I can find and I don't want to give the impression that I'm free to solicit requests. Similarly, I haven't shared my documentation of bug reports and feature requests because I don't want to be placed in a position of responsibility for acting on everything that comes my way. I understand that mod groups find it useful to maintain public lists of stuff like that and that it's helpful for the users to see what's been reported already. If there were more people than just myself working on this I'd definitely go that route but I'd prefer to keep things a bit more informal and make sure the project remains fun for me to work on and not a responsibility. Hope my position is understandable!
I'm going to look into optional tasks, but due to how they're selected based on the AO terrain available whatever options I implement would have to be more like suggestions to the system and would be overrode in the case that no valid locations for the selected tasks were found.
How's your stuff licensed? How do you feel about someone else using your work as a base to create an alternative, different sets of missions and what not?
You'd get the honour of making the base(so does the guy that made the framework), and you don't have responsibility of maintaining those alternative versions.
Win win!