Whimsykiller

I wasn't sure if this was the proper forum, and couldn't find a thread with similar issues. My issue is, however, that Headless Client crashes almost immediately upon start of the mission on my current version. 1.63 broke a ton of things for my group when it came about a year ago, and the massive amounts of script errors make my game virtually unplayable as well. We use the rolled back 1.62 on steam, as it's much more stable, and just use the beta patches available via beta_oa to make the difference up for things like shacktac hud to work correctly and all that. I tested it and rolled forward to 1.63, and it worked fine, just the aforementioned script issues messing with a lot of our scripts; so it was worthless anyway. Play with Six has a very limited amount of versions, so we're currently on 1.62.0.108074-alpha. Is there a version of these betas where HC works correctly? People started using it years ago so it clearly predates the official 1.63; I worked real hard on setting it up and am dejected to see it was all for nothing. Any advice would be appreciated.

Do you specifically need only 3.0.11 for the backwards compatibility to work? I have 3.0.11.1 and when I go to enable the plugin it says 'Plugin failed to load: failed to open plugin" EDIT: In case anyone is a lazy piece of stuff like myself and didn't explore the folder, look in 'Extras/Shacktac' and that plugin works.

Who are we? Freedom Force Alpha Alpha Alpha is an Arma 2 community that aims to play the game in a serious and 'tactical' manner, but is in no way a hardcore-milsim community. We do not have set or static roles; what you play varies from mission to mission and the only thing restricting you is your ability to play said role and if you can get to it first. The idea is to create a comfortable environment where everyone can come, play some serious Arma 2, and have a great time without having to worry about people being jerk. Everyone plays in a similar style and manner while having a coordinated and familiar command style that is easy to understand. We also aim to have an active community who play the game regularly, as Arma 2 is still a wonderful game with a massive amount of content at our fingertips; even if it isn't the baby of the family anymore. What we seek: Active: We are an active community that plays two times weekly, our weekly Saturday game is considered to be the main event and we seek people interested and willing to attend regularly. There's no room for flavor of the month-ers. Respectful: As a community we are here to play Arma 2 in the style that we have chosen. There is no room for shitty 'group politic' type drama, nor is there room for insults or treating others badly. We're here to enjoy ourselves, and everyone should have equal chance at that. Serious-Minded: Our goal is a serious and 'tactical realism' feel without going over the deep end and finding ourselves in Milsim waters. Those wishing to join should be interested in that as well, and willing to contribute to that experience. Dedicated:The experience by the community as a whole each session is dependent on the individuals participating, thus making it everyone's responsibility to help make that the best experience we can. Skill level doesn't matter, that can always improve. Our Schedule: Saturday, The Main Event: 12 PM, every Saturday Tuesday Session: 4 pm, every Tuesday Our Modset: We are an ACE/ACRE community, and the full extent of our modlist is view-able on the steam group page. How to join: Our joining process is simple, add me on Steam here, and I'll contact you as soon as I'm able, once you have the mods ready you're free to join us on our next session for a trial run to both see how you like it and how you fit in with the intent of the group.

Two squads in Takistani are forced to fight to Sakhe to steal their tires!

There is not a single bug in arma 3.

Mission where the CDF are a stand-in for Mexican soldiers against Cartel-men. Leads to some intense firefights.

Different kind of mission ends in a hurried run from a seemingly endless amount of pursuers. A different feel than normal, terrifying.

I've just started trying to get into DAC, and I edited the creator config to change the unit name requirements from all the 's' stuff to my usual names for units 'PltCO' for Platoon Commander, 'PltMED' for Platoon medic, "ASL" for Alpha Squad Lead, etc. I loaded in, and now I get this error, and it doesn't create units or do anything that it should. http://i.imgur.com/vShPaqB.jpg (365 kB) I haven't touched the script it references, and have compared it to the base one, and it is exactly the same. I don't understand the issue, or how to circumvent it. DAC works fine normally when I try the example missions, so the only thing I've changed is the naming part. The AI also spawn correctly when I play as an unnamed unit, and it just gives the 'YOU DIDNT NAME ANYBODY' warning. This is on the script version. *Edit* I figured my issue out on my own, I had typed out a unit name incorrectly and also included a dash, fixing that in the Config Creator solved my issue. Didn't delete post just in case someone else does the same.

Does this work well with Zeus? I know the bootleg port from A2 to 3 of ACRE didn't work with Zeus.

I don't really feel like the first part of that message was necessary, but thanks for the response regardless. I happen to be running that version of the beta patch, and it does not work for many of my players, only a select few. The later versions in six are all labeled 'Alpha', do any of those work particularly better than the others?

My community had to roll back to 1.62 to continue playing as we would, due to the latest update breaking a lot of things for us. This has resulted in the ACE settings no longer saving by themselves, and the ACE Clippi being needed to save our settings. (Before, as long as identity was set in Six it would remember) and this doesn't even work for some people, who must reset their settings every time they launch the game. Any way to circumvent this?

My community has rolled back to 1.62 due to the latest update really messing with a good portion of our scripts and making it difficult to play. This has the nasty effect of making ShacktacHUD not work unless you roll it back to a pre-STGI format. I was a huge fan of STGI, and would like it back. Anybody know how?

Is there a way to limit what units can repair?

Is that for you to fix or us to fix? Right now the update has caused me to have to switch to a VDS for my server and downgrade to 1.62, but that causes some issues of it's own. So a more stable version of the latest would be preferable.

No, it happens when I run missions myself, as well.

The update has caused the scripts to be read differently it seems, not only does every single script (whether it be ACE or UPSMON or something similar) report as an error, even BIS scripts report as errors, but in LEA the minute it gets to an empty slot (or sometimes even filled slots) it suddenly breaks the script and stops kitting them out. We are working on trying to repair this (making our own scripted loadouts suffers the same issue, as I spent a long time yesterday making a loadout script only to see it suffer the same issue. The only solution is making a script for each unit, or doing it in their inits. This is less 'a single update breaking the community' and more, 'a single update that breaks a lot of things within the game, causes many players to have the greatest issue just STARTING their game, and making it a hassle just to play a session being a very high possibility for breaking the foundation of the community. If we cannot play Arma 2, it is hard to be an Arma 2 community. If you have an alternative way to loadout units that works without being a giant hassle, I would love to hear it. I've also contacted Major Shepard to see if he can figure out what is causing the issue. Either way, this update has brought nothing to us that we felt we needed. (Nothing was broken before.)

I do not have any missions without addons, unfortunately. However, the error that I get while using my modset (which includes ACE, ACEX, ACRE, the shacktac mods, some islands, etc) http://i.imgur.com/mhN6P8T.jpg (636 kB) In addition, EVERY SINGLE SCRIPT gives errors, whether or not it works. This update has caused every script to be reported as an error.

The update has broken LEA (which my group uses to script our loadouts) and in addition has just introduced so many many problems for people to start up their game or join the server. It seems like a lot of unnecessary changes, and this update threatens to tear apart my community, which has been going strong till now. We can't just sit on our hands until BIS fixes their shit.

This update has completely broken a lot of the stuff my community uses (including our loadout scripts which use LEA, which are heavilly necessary for our play) and has caused a lot of players issues in joining or finding our server, or even just starting up their game without a myriad of problems or crashes. Whatever the update has done to scripts, it's made it incredibly unplayable for us. Seems like a slap in the face for people who stayed with A2, you completely break our game and there doesn't seem to be much going on to fix it.

So how should we tackle this? Is this something we can fix on our side, or something you can fix? Or do we have to just try and get BIS to stop breaking our game?

Yes, just yesterday. They swtiched to 1.63 nonbeta, to go with switching to Steam since Gamespy has died. From my digging, I and my community have found that LEA works provided all slots are filled, however the moment it comes to a slot that is not filled in game (say we choose not to use a slot) that it was scripted to loadout, it stops working and any slot after the empty one will not have a loadout, while every one before it will.

I PM'd Shepard but thought I'd also post here in case anybody has a solution. The latest update has completely broken LEA for me and my community, all of our loadouts, for about 95% of the missions, do not work. Some missions work fine, while others don't work at all. In many, one unit out of 40+ will have its loadout. It's incredibly damaging to our community, as we employ many things that rely on the loadouts. If LEA cannot be fixed (or if a fix cannot be told to us) is there an alternative?

Updating to post what has to be one of the best missions I've played so far, even if an accident lead to the UPSMON debug markers being on. Oh well.

There is an orange button with a few dots next to the 'UPDATE' button if it wants to update, click that and you can select 'play without updating'.

I'm not certain if this has been said yet or not, but Esbekistan wants me to download three other islands now (Clafghan, avgani_iraq, and afghan_village_opteryx) This is a recent thing, and I've just been launching without updating for now, but it's annoying as I'd like to add new mods to my list, but don't want to download three unwanted islands. Is there a way to get around this?