AI War Wiki Updates (now automated)

[Diazo]

Alright.

I'm starting a new thread for the wiki stuff as I have the automated updates working 100%.

It is just placeholder text, but my fighter 5 test page was generated 100% by my update code, no manual tweaking required.

I just have to copy-paste my table generating code from my previous version in and we are good to go.

However, before I update all the ship pages on the wiki, I'm throwing this out so everyone has one last chance to suggest any changes.

For reference: The Fighter page.

My update code in question only affects the tables in the "Base Stats" section, so that is what I'm open to suggestions on at the moment.

Previous wiki thread here.

D.

[Bognor]

Splendid 

Are the base damage numbers accurate?  4,080, 8,160, 12,240, 16,320, 20,400 would be linear, but I'm seeing 4,080, 8,160, 12,200, 16,200, 20,400.  (I understand stats for turrets of different marks are just slightly off linear, so maybe it's the same for Fighters.)  Same comment applies to Cap DPS, but I presume that's a derived stat.

Mark III knowledge cost is now 4,000, not 6,000.

[Diazo]

Splendid 

Are the base damage numbers accurate?  4,080, 8,160, 12,240, 16,320, 20,400 would be linear, but I'm seeing 4,080, 8,160, 12,200, 16,200, 20,400.  (I understand stats for turrets of different marks are just slightly off linear, so maybe it's the same for Fighters.)  Same comment applies to Cap DPS, but I presume that's a derived stat.

Mark III knowledge cost is now 4,000, not 6,000.

Just double checked, the Fighter does in fact have slightly wonky damage numbers, the data files have the 12,200 and 16,200 numbers. This matches what I see in the game so yes, it is accurate even if it does not follow the linear progression most mark levels have.

And I've updated the K costs, it has simply been that long since I have done any updates to the wiki as automating everything will require touching every page one last time manually and I was not going to bother updating the pages twice, once for the K costs and once to automate them.

Debugging the combined code (the new automated code and the old table creating code) is taking longer then expected so expect the first new pages up tomorrow morning.

D.

[Diazo]

Okay. The first few pages are up.

Fighter
Bomber
Missile Frigate
Acid Sprayerr
Anti-Armor
Armor Booster

I've checked the data on these 6 pages myself and I'm going to start carrying through to the other ship pages now.

However, as this procedure is now automated, I'm not going to manually check that the data is correct so if you see something off let me know please.

If I just update the page it is roughly 10 seconds, most of that waiting for the page to load. If I stop to check the data it's in the 60-70 seconds per page range and with the number of pages to do I want to be as fast as possible.

I'm going to get through all the fleet ships first, I'll update this thread when I move on to the starships.

D.

edit: Hmm. Is the Neinzul Cockroach player buildable at all? I'm getting a ship-cap of 1 from the data files which is typical of AI only ships. Anyone know for sure?
Are Mk V Neinzul Younglings supposed to attrition or not? Some of them do and some of them don't according to the Abilities entries in the data files.

edit the 2nd: And fleet ships done already. (At least the ones already on the wiki, still need to add the ones from the new expansion.)

[Orelius]

IIRC, cockroaches come exclusively from an AI homeworld guardpost, so they can't ever be made by players.

[Bognor]

I don't know any way for humans to get Neinzul Cockroaches.  They're spawned by a particular core guard post.

Since 6.039 all Mark V Neinzul younglings are supposed to self-attrition.  But Neinzul Scapegoats and Neinzul Railpods are "mature" Neinzul organisms that do not self-attrition at any mark.

[Diazo]

K, thanks for the info on the cockroach. It was previously on the wiki as player buildable so....

On the Youngling Mk V Self-Attritioning, it seems like some do and some don't.

According to the data files I see the following for the Mk V younglings:

Commando: Self-Attritions
Firefly: Does not
Nanoswarm: Self-Attritions
Tiger: Self-Attritions
Vulture: Self-Attritions
Weasel: Self-Attritions

Okay, all but the Firefly still self-attrition I guess.

Keith: I'm pulling this from the 'Abilities' column in the data-export for these ships, I'm assuming this is accurate for in-game so it looks like something got overlooked here?

D.

[Bognor]

I'll bet Fireflies got missed because of the anomalous "ShortName" they use for behind the scenes stuff: "Y-Fire" as compared to Yng Commando, Yng Nanoswarm, Yng Tiger, Yng Vulture, and Yng Weasel.  They're also called "Youngling Fireflies" in wave warnings whereas the others are called "Neinzul Youngling Commandos" and so on.

[doctorfrog]

I'm not the type of person to look up details in a wiki for a video game, but this isn't bad. Reminds me of the Civopedia a bit, everything you need to know about a given unit or tech is presented in a brief, well-organized 'pedia entry.

Say, now there's an idea...

[Diazo]

heheheheHEHEHEHEBWAHAHAHAHAHA!!!!!

ahem.

I have grand plans for the wiki, including a lot of higher level overview stuff like what I think you are talking about.

I started with the individual unit pages because they are going to be the most time consuming part and they also serve as a double-check to make sure I've missed nothing as I can look at the data file and go "these units are done, these still need to be worked on".

Once I get the units done, I'm going to get a skeleton of the higher level stuff setup so navigation between pages and stuff works and then start asking for other people to help out with filling in the details on the individual pages.

Hopefully that is only a couple weeks out now that I have the procedure for automating the updates to the individual unit pages as that leaves me a lot more time for other stuff.

D.

note to self: I was unable to automate the Riot Control SS Modules stat blocks due to their layout. Need to double that their current stats are correct tomorrow.

[Aeson]

Just wanted to let you know that there's a typo on the Zenith Devastator page, in the "How to use in your fleet" section:

The last sentence uses "is" instead of "its" when referring to the speed of the Zenith Devastator.

[Diazo]

Bleh.

I'm getting a

Sorry! We could not process your edit due to a loss of session data. Please try again. If it still does not work, try logging out and logging back in.

error on the wiki. Can someone else with access please try to edit a page?

I cheated and checked from work this morning and am getting the same error so something is up with the wiki. I'll see what I can figure out.

D.