America's Army 2.8.3.1 Released

[LadyHawk]

I have all the Linux files and release notes if you need them.

Do you have an ETA on the update for this?

[darren]

If you already have the files extracted from the windows patch, pm or email a link to them, I don't have AA installed right now since my laptop is out of space. I didn't see a linux server update so I assume what is needed is in the aa_patch_283to283_1.exe patch ?

[LadyHawk]

Here are all the Linux and Windows files. The Linux ReadMe download is also included on that page.

http://the-hawks.net/forums/main.php?pageid=aadownloads

[darren]

The readme refers to this file to coincide with the maps file as being new for 2.8.3.1, however I can't find it anywhere:
6B9114ED63A1CFFFA22FA8007EFD5E66 AA2831_LinuxRuntime.zip

Google/Yahoo/Lycos all returned zero hits for it and I didn't see it on the downloads page. Am I overlooking something obvious ? Thanks :!

[LadyHawk]

WOW. You didn't over look anything....I forgot to put that file on the download page....It is there now.

http://the-hawks.net/forums/main.php?pageid=aadownloads

[darren]

Thanks, a bit closer now, but when I click on it, it takes me to:
http://www.the-hawks.net/ccount/click.php?id=67

Which then says "This ID doesn't exist!" .

[LadyHawk]

ok. I don't know how I deleted the link out of the counter software, but I redid it and it is working now.

Use the link off this page:
http://the-hawks.net/forums/main.php?pageid=aadownloads
and it should work now.

(Just chalk it up to having a long day with 5 kids)

[darren]

Hey, sorry for the delay. The new package should be available on cpgs.network3.net and hopefully other mirrors before too long. Let me know if you see a problem with them

[LadyHawk]

Can you so a upgrade without having to start from scratch ?

[darren]

I've been thinking about a realistically maintainable way of doing small upgrade packages for awhile now. The problem is essentially me not having enough time to make update packages for each server. While in the beginning it's not bad, once a server packages has a few updates, you have to maintain many update packages since people don't always update at once. For example, if you had Postal 3 v1.0 and in the next year they released 5 updates, 1.0 being the initial release followed by 1.1 1.2 1.3 1.4 and 1.5 .

So with the first release, easy, no problem:
1.0 -> 1.1

Second update.. well, some folks may not have updated to 1.1, but some have, so they both need updates:
1.0 -> 1.2
1.1 -> 1.2

Now with version 3, there are 3 possible versions we could be coming from:
1.0 -> 1.3
1.1 -> 1.3
1.2 -> 1.3

Now 4:
1.0 -> 1.4
1.1 -> 1.4
1.2 -> 1.4
1.3 -> 1.4

And a new one, 5
1.0 -> 1.5
1.1 -> 1.5
1.2 -> 1.5
1.3 -> 1.5
1.4 -> 1.5

So with each server and update, there is a new package to maintain. Multiple this by the total number of supported servers and it gets nasty pretty quick, Additionally, and a much larger headache, is the issue of the configs. Some of these updates (AA for example) causes fairly large changes in the config files, where new data must be added, old data removed, and the upgrade paths from each version to the next must be kept track of. This is a logistical nightmare for the long term. The time it takes to download a full new server package, set up any mods (for which conflicts would/could not be considered in upgrades) and reconfigure is usually not that bad. If you are deploying multiple servers, the pkg script that comes with cPGS now allows you to pre-bake your own packages with mods and configurations already set up. If you can think of a way to negate all these problems and still making it worthwhile, I'm all ears

[haswalt]

I see the dilema Darren and have been thinking about this myself.

One consideration i had was since the patches are small, how about a dedicated update server purely for small patches. I've been playing with your code as part of teh icecast system i'm working on and i tihnk if someone (i wouldn't mind doing it) kept an up to date repository of all update files, download/extract and patch in one function rather than prestorying them on the server as they are small.

Also maybe give admin the option of setting which patches are to be done from local files and which from update server? So if there any larger patches that the owner doesn't think will be fast enough to download, they can download it once and set the potches to be taken from local files.

Then the patch button would be available in the cPanel end to customers, since they can then update when and if they want. I have also known some of my clients to not want a patch as their small private servers for them and their friends either hav mods that don't work on later version or use and eploit to have more fun.

Just a thought

[LadyHawk]

I think only offering patches for the most current release would be a good option. Why should you have to do all the work. If someone wants to skip updating there server, then it is up to them to do the 1.0 to 1.1 and then the 1.1 to 1.2 one at a time. There should be no reason for you to have to do all the patches that you listed. In this case you would only have to do the 2.8.3.0 to 2.8.3.1 and then the 2.8.3.1 (to what ever version AA decides to name the next one).

[haswalt]

That's why i think making the patches available from an update server to the customer much the same way as the full game packages are available for us to download and install will reduce the time and effort for the admin and alloow more flexibility for customers. Perhaps it wuld be prudent to offer an option to be automagically patched since some customers would not want to have to patch themselves.

[LadyHawk]

OK I have been so busy I have not had a chance to install the new 2.8.3.1 server and get one up and running. When I go in to the control panel I get the same error that I got before (that you fixed Darren)...

Misconfiguration detected, please alert support.

I do this all in the control panel, but I am pretty sure you fixed it via command line last time....

Give me your secret :P

[LadyHawk]

I think I figured this out.....