1) Added L60 Towers
2) Automated Builder Hut Finish Level through a series of questions
3) Altered conditional formatting for builder input levels so it doesn’t go RED if you haven’t filled out all cells
4) Fixed row height issue when downloading into excel
5) Player Level calculation was sequenced incorrectly. Amoeba table verified & correctly altered in document to reflect the actual XP required to level. Very minimal changes overall except in the lower levels or when starting a brand new account from level 0, it ended up showing 1 level too little
Thanks to @Marez, @Spooky and @Nuffle for testing the excel compatibility. Thanks for your patience and hard work on this as always!
If you find errors or links that are not working please message me and let me know, i will try to update this ASAP when errors are discovered
@mechengg thank you for the hard work and effort, planner looks great. Haven’t caught any bugs yet, but will let you know if something shows up
One suggestion I have is to add an option to not count the timers needed for a build but count the points for cases where a player starts a build at the end of the event that they want to leave building without using speed ups.
It was on the previous list of “nice to haves” to add to the planner. I’m still trying to find a way to cleanly implement it for a future revision so “Yes” it will definitely be added to a later revision, just can’t confirm which one yet.
To address your concerns the reason i initially created the “flag system” as such is that I do personally feel (and want to pass onto others) that it isn’t a good idea to over level compared to your roster strength. If you don’t have enough research eggs and you want to say upgrade your towers past level 41, you will run into a red flag and perhaps it will be an indicator that you need to slow your progress down until you get your builder hut leveled up a bit more.
That being said, i could possibly find another way to integrate these “flags” in a different way by requesting more user inputs (such as castle island levels) and comparing them to what the user currently has vs what they ideally should have for their level. It could work out even more in my favor by them seeing that they are X levels behind in storage and X levels behind in hut. Then i can make recommendations to hold off on leveling until your hut reaches certain tiers.
I will come up with a few different scenario’s for the next release (a few months away probably) and run them by my peers for their review and comments to see if they fit the overall theme of the planner and we can go from there
I wasn’t even aware there was a rider construction time discount. Is it additive like the other research times? Or could you get me a screenshot with/without for a few different tower levels and i can figure it out for myself?
Pearls/embers/shards are currently not separated (would have to put in different columns…so would expand the sheet) so i’m not sure that it would overall give much useful information AS IS. It isn’t too onerous currently to do the manual verification vs your game (just check the single line item) but i can certainly put it on the list of items to consider for next time. This one would probably require the most changes out of all the suggestions presented thus far.
Like instead of selecting “Archer” you would select a picture of an archer tower from the drop down menu? What benefit would that have? I think it would honestly be harder for the user to easily check which tower it is lol. All of the data is present in the bldgdata tab of the sheet if you look there and unhide the correct section. The Amoeba columns are all in grey with the custom edits in the white columns to the right of the copy/paste amoeba section.
As of right now there is no attack/defense data on the fire flaks in amoeba. They are all assumed to take the same amount of shards/wood/time to complete (unlike the perches which varies between 1-2-3 with costs and upgrade time. So if you have a dark flak and fire flak just use two elemental flaks. I can look into separating them once Ice Flaks come out and/or if the cost/time is different between the different elemental towers. As of right now i’d just be copy/pasting information.
Thanks again for your comments and i will log them and keep them in consideration
Thanks @mechengg I am using an old version of fort planner. I usually add a formula to your sheet in order to maximize event points. Simply put, it is event points per 1 day speedup usage. Higher the rate, better the result. Same logic can be applied to total xp column.
For example, for row63 :
This can be helpful to all community, so i also want to share a ss with it.
However i absolutely despise that column and everything it stands for. You should be building your base for defense purposes and not to maximize points. Choose your layout properly, choose which towers are optimal to upgrade and the points are simply a by-product of what you get out of it.
So for that reason on principle alone i will never be adding it to the standard Fortification Planner. Feel free to add this to your own personal planner for your own purposes but i’m not going to have anything to do with this sorry. I hope you understand my position on this.
Thanks for the feedback. I am building my base for defence purposes of course, This ratio helps me a lot for the event when i am short on timers. It actually shows that building higher level towers is better than bunch of low level towers. If ratio is too low for a tower, it means build that tower at the end of event except for builder since farms and mills are great in fort event.
This is your planner @mechengg Do as you wish.
Have a good day.
For Excel users:
I don’t really use google sheets so I downloaded it as an Excel File and I was surprised that most of the code worked as intended for Fortification planning.
The only codes that don’t work in Excel is the Player Level Finish, the XP to Level Finish and all columns of the Base Information.
The only thing I was interested in was the Player Level Finish to know what level I will be after the event. So I simply edited P4 (hidden column) and only used the basic lookup function (the same code which is used in the old Fort Planner). Works perfectly fine for Excel now
Most functions work in Excel too.
@mechengg Thanks for keeping this very useful tool up to date!