Quick update. I'm still working on the update, and as I suspected, it's a beast to get the dual-upgrade slots working correctly. I won't have time to get back to it until late this week or Sunday. Sorry for the delay. Spreadsheets were never meant to be turned into applications.

2 hours ago, Thraug said:

Quick update. I'm still working on the update, and as I suspected, it's a beast to get the dual-upgrade slots working correctly. I won't have time to get back to it until late this week or Sunday. Sorry for the delay. Spreadsheets were never meant to be turned into applications.

At least you are doing it - thanks for that!

Quick question - in the sheet, when recording assaults, you have an 'Outpost Defense' checkbox - what's it for? Specifically outposts? 'Cause it affects campaign points, but I was unaware that outposts specifically are treated separately from the neutral planet and base assaults.

Hi, I just looked into you marvelous pice of work. Maybe I dont find it, but is there a way to track recource points for special assaults?

I'm still working on version 4.0. super-hectic work deadlines and familial obligations have held me up. I hope to work on it next week.

Pics that hopefully answer the questions above:

Another pic:

I'm unsure if an extra point should be added to a Outpost defense. I have to go over the point allocation rules again. The spreadsheet knows if a base is being attacked, but not an Outpost, so this column is used to indicate a Outpost defense. At one time I thought that's the correct way to score, but now I'm unsure.

Is there an easy way a user could increase the number of fleets? We are about to start another campaign and we are borrowing someone's suggestion of making 9 fleets (hopefully 10 before we finish) and it would be awesome to use this for our expanded fleets. I am ok with excel but nothing like what you have created.

2 hours ago, Cusm said:

Is there an easy way a user could increase the number of fleets? We are about to start another campaign and we are borrowing someone's suggestion of making 9 fleets (hopefully 10 before we finish) and it would be awesome to use this for our expanded fleets. I am ok with excel but nothing like what you have created.

Easy? No, sorry. It's not even easy for me and I wrote most of the spreadsheet.

The majority of the difficulties with maintaining this spreadsheet, and adding data as new waves are released, comes from the ship upgrade validation. Meaning, making sure the upgrade drop-down menus for a ship are selectable or not, and ensuring illegal choices are not made. An example would be disallowing the selection of an Offensive Retrofit on a ship that only has one Offensive Retrofit upgrade slot and the user has already chosen the Boarding Troopers upgrade, which consumes the Offensive Retrofit slot. These validation checks are not implemented in a way that allows for the easy addition of new fleets or new wave data.

I added the ship construction portion late in development, as an after-thought, and struggled getting it to work correctly within the spreadsheet framework. Looking back, I should have implemented the entire ship construction portion in JavaScript (Google App scripting actually) in a more extensible way, allowing for quick and easy wave data to be added. Or, not even bothered with upgrade checks and leave it to the user to make sure they didn't make an illegal choice, such as selecting a Support Team upgrade on an ISD.

Unfortunately I do not have the time to maintain it beyond releasing the next version containing wave 6 data. I'm close to done but had to mothball it the past 2 weeks due to other obligations. I'll have it done ... "soon"! Sorry for the delay.

That is what I figured. Thank you for all the work.

Quote

Easy? No, sorry. It's not even easy for me and I wrote most of the spreadsheet.

The majority of the difficulties with maintaining this spreadsheet, and adding data as new waves are released, comes from the ship upgrade validation. Meaning, making sure the upgrade drop-down menus for a ship are selectable or not, and ensuring illegal choices are not made. An example would be disallowing the selection of an Offensive Retrofit on a ship that only has one Offensive Retrofit upgrade slot and the user has already chosen the Boarding Troopers upgrade, which consumes the Offensive Retrofit slot. These validation checks are not implemented in a way that allows for the easy addition of new fleets or new wave data.

I added the ship construction portion late in development, as an after-thought, and struggled getting it to work correctly within the spreadsheet framework. Looking back, I should have implemented the entire ship construction portion in JavaScript (Google App scripting actually) in a more extensible way, allowing for quick and easy wave data to be added. Or, not even bothered with upgrade checks and leave it to the user to make sure they didn't make an illegal choice, such as selecting a Support Team upgrade on an ISD.

Unfortunately I do not have the time to maintain it beyond releasing the next version containing wave 6 data. I'm close to done but had to mothball it the past 2 weeks due to other obligations. I'll have it done ... "soon"! Sorry for the delay.

Something that would help with ease of updating for new expansions would be to reconfigure how you have your data sheet. Because it is in a single column format every time you add new ships it displaces what is below them. It doesn't hurt the data validation drop down menus, but the conditional formatting isn't automatically updated. If you make separate columns for each category with your REGEX validations AT THE TOP above the list (so adding new waves doesn't shift the referenced cells) you should be able to easily add new ships and upgrades while being able to easily find and update the REGEX equations without needing to mess with the conditional formatting. I haven't looked deep enough into your setup to see how you are handling titles other than having duplicates of the base ships, but you may be able to stop duplicating as well.

As for the double upgrade slots, a suggestion I have is including them as their own separate combo upgrade with their own REGEX validation for what ships can use them. Set a conditional formatting that sets the cells for the types used to gray. I would suggest always using the first one if a ship has two available so you don't need special cases and can set it on an entire column range.

Personally, I don't feel like all the fleet building validation is needed because there are already several good ones online. I see your sheet as mainly a way to track the status of the fleets and the game itself and input my fleet data after I built it elsewhere. The important part is all the campaign specific stuff you built in the Team Status and Systems Tracking sheets.

I'd go about it myself, but I don't have all your knowledge of what you have connected and will probably end up just breaking it. I might still give it a try though.

Thanks for your work in building it.

Thanks "player2901714", all very good solutions, and I will use, or have used, quite a few of those in the upcoming version. I also learned a lot about GScript's Property Service , and embedding ScriptProperites, and that has helped solved a few other issues.

I've been waiting for FFG to release more Wave7 articles so I can release a version of this with Wave7 items, but they are taking their time. I thought for sure we'd have a true M75 article by now. I may just release it just for Wave6 for now. Sorry for the delay!!

Has anyone made a version of this with support for the wave 6 admirals? Starting a new campaign and we have both a Leia and Sloane fleet. I was trying to edit the data sheet but I'm concerned I will mess up all the field validations.

Running version 3.5.

56 minutes ago, KuniYasashii said:

Has anyone made a version of this with support for the wave 6 admirals? Starting a new campaign and we have both a Leia and Sloane fleet. I was trying to edit the data sheet but I'm concerned I will mess up all the field validations.

Running version 3.5.

@Thraug , the creator, is currently working on it. As it will be his last edition (given the work it requires to update) he was waiting for wave 7 articles to bring it as up to date as possible before release.

Yeah I had seen a reference to 3.6 in the instructions page for it so I wondered if I just had an older version.

No, 3.5 is the official version.

I'm still here, and yes, I was hoping that by now FFG would have released Wave 7 info so i could include it in the next, and unfortunately final, release. I'll give FFG a week or two to release wave 7 info. My Jedi senses (and my foolishness) are telling me FFG should be releasing more wave 7 soon. I hope. Please?

Sadly they've delayed wave 7 until next year:

https://community.fantasyflightgames.com/topic/262803-one-year-one-release/?do=findComment&comment=3070394

I was hoping for a Profundity under the Christmas tree :(

Shazbot!! I'll release a new version, sans wave 7, asap. Oh well.

No Quasars?

2 hours ago, comatose said:

No Quasars?

Next version will have both Quasars and Hammerheads. I should have time tomorrow to work on this, and release it soon. No wave 8 due to FFG delay.

Appreciate the sheet btw. It makes tracking everything in the campaign so much easier for my group.

I spent most of yesterday working on it and was able to get most of it done. I'm hoping to get back to it tonight (Empress permitting).

Work continues on v4.0. I haven't ditched this (yet!).

The majority of my time (99.99%+) has been spent overhauling the ship builder's upgrade validation "system". The in-spreadsheet Conditional Formatting checks were far too restrictive for the latest set of upgrade options (Boarding Trooper/Engineers, Tua, Phoenix Home title, etc.) so I moved the entire upgrade validation and control "system" to script, via a custom upgrade handler/router I created. In short, this will allow for ship upgrade validation (and control) for anything(?) they introduce, assuming it can be handled in JavaScript.

While it'll be much easier to introduce new ship and upgrades to the spreadsheet, it will require at least some JavaScript knowledge to implement, or very good copy and paste skills. I first implemented it using the newer "Class" syntax in the JavaScript ES6 specification, but this doesn't seem to be allowed in the Google Script world, so I instead implemented using the prototype-based class inheritance pattern. It's overkill, but I wanted to learn how to use it, so there you go!

I really should have just removed ship building validation, making the spreadsheet super simple to maintain, but I'm far too stubborn to let it get the best of me.

ETA? Probably next week. I won't be able to wrap it up until the Thanksgiving holiday is over.

Thanks for the work on this. You've done a amazing job. I'm sure most users would be satisfied with something simpler but you've really finessed the balls off this!

Very amazing job! This sheet was very usefull. Thx for your time.

I don't see Disposable capacitor in the category Upgrade - Offensive Retrofit...