CLI and Publish Tests

docs/Tasks/Add Co-op objective reference.md

@@ -0,0 +1,6 @@
+---
+type: Task
+status: Blocked Backlog
+category:
+---
+The procedure co-op mode is definetly very fun. Need some reference of all the possible objective types. Like gather pyre, hold certain points, kill rae golems, kill bases, etc.

docs/Tasks/Add a Timeline Editor.md

@@ -0,0 +1,7 @@
+---
+type: Task
+status: Backlog
+category:
+---
+I should be able to add a Legion Hall earlier in the timeline, like if I change my mind, and decided I wanted 2 instead of 1 before making a Soul Foundry
+

docs/Tasks/Add an Ability to Favourite Data.md

@@ -0,0 +1,7 @@
+---
+type: Task
+status: Backlog
+category: Feature
+---
+Let me heart a entity to save it to a different screen for viewing.
+

docs/Tasks/Add some cooldown reference.md

@@ -0,0 +1,8 @@
+---
+type: Task
+status: Blocked Backlog
+category:
+---
+How many spells can I cast? How long does it take to regen mana?
+
+Use the same logic for a damage reference. How many hits with attack before killing enemy.

docs/Tasks/Allow to Always see Advanced Options in Calculator without pressing Space.md

@@ -0,0 +1,6 @@
+---
+type: Task
+status: Backlog
+category:
+---
+Make it a Toggle

docs/Tasks/Army Calc UI.md

@@ -0,0 +1,9 @@
+---
+type: Task
+status: TODO
+category:
+---
+![[Pasted image 20260601083127.png]]
+
+- Attacking Time should be Travel time plus Completed At time.
+- Built units should show in the Army units built component

docs/Tasks/Army Display Split.md

@@ -0,0 +1,8 @@
+---
+type: Task
+status: TODO
+category:
+---
+![[Pasted image 20260601093510.png]]
+
+- Split to be Total Alloy and Ether spent on raw Army Units

docs/Tasks/Auto Build consideration in Calculator.md

@@ -0,0 +1,8 @@
+---
+type: Task
+status: Blocked Backlog
+category:
+---
+In the past, I recall respectable pro player vounching for the value of the auto build.
+
+It's probably a good idea to see how much the auto build could generate on an unefficent build order to represent time spent microing

docs/Tasks/Basic Build Order Sheet.md

@@ -0,0 +1,4 @@
+---
+type: Task
+status: Backlog
+---

docs/Tasks/Build Clear should clear out more stuff.md

@@ -0,0 +1,10 @@
+---
+type: Task
+status: TODO
+category:
+  - Bug
+  - QA
+---
+![[Pasted image 20260601083005.png]]
+
+Fix bug where Entity View is not being cleared on clicking the Clear Build Order button

docs/Tasks/Change Ctrl + K Hotkey to something that doesn't conflict with Edge or other browsers.md

@@ -0,0 +1,6 @@
+---
+type: Task
+status: Backlog
+category:
+---
+Alt + K?

docs/Tasks/Changing Factions and Immortal should clear out build.md

@@ -0,0 +1,10 @@
+---
+type: Task
+status: Working On
+category:
+  - Feature
+  - Bug
+  - QA
+---
+- Should clear out current build. Should show a warning dialog if your going to clear out your current build
+- Shouldn't show an error dialog if your not clearing out a build. Add a unit, then clear it out, before testing to ensure this works

docs/Tasks/Create Automated Tests.md

@@ -0,0 +1,5 @@
+---
+type: Task
+status: Done
+category: QA
+---

docs/Tasks/Create Mobile Calculator UI.md

@@ -0,0 +1,6 @@
+---
+type: Task
+status: TODO
+category:
+---
+Doesn't care about keys. Show big buttons.

docs/Tasks/Ensure build order gets greyed out past the attack time. Clicking the cancel button will wipe the entire greyed out timeline..md

@@ -0,0 +1,9 @@
+---
+type: Task
+status: TODO
+category:
+---
+
+![[Pasted image 20260601082954.png]]
+
+- Ensure build order gets greyed out past the attack time. Clicking the cancel button will wipe the entire greyed out timeline.

docs/Tasks/Entity Click View Tests.md

@@ -0,0 +1,9 @@
+---
+type: Task
+status: TODO
+category:
+---
+![[Pasted image 20260601083046.png]]
+
+- Make sure the dialogs and sub dialogs work
+- Ensure the displayed unit changes when clicking on a different unit

docs/Tasks/Fix Entity Recursion Error - Parent.md

@@ -0,0 +1,5 @@
+---
+type: Task
+status: Done
+category:
+---

docs/Tasks/Fully Test the Build Calculator.md

@@ -0,0 +1,5 @@
+---
+type: Task
+status: Backlog
+category: QA
+---

docs/Tasks/Get AI to Add easy Test Tasks.md

@@ -0,0 +1,16 @@
+---
+type: Task
+status: Done
+category:
+---
+Consider Playwright features we can use to create obvious tests to our test project in the Playwright folder.
+
+For these considered tests, create markdown files in the "docs\AI Gen Docs" folder. 
+
+They should have the front matter of:
+type: Task
+status: AI Gen TODO
+category: QA
+isAgentGenerated: "true"
+
+Describe what the test is in the contents of the markdown file, and what special feature of playwright it's using, if it's using something special in comparison to what we already have.

docs/Tasks/Helper Tutorial Info Improvements.md

@@ -0,0 +1,40 @@
+---
+type: Task
+status: Working On
+category:
+  - QA
+  - Feature
+---
+
+![[Pasted image 20260601083333.png]]
+
+- Ensure referenced data is taken from the database. Unit names and costs are currently hard coded.
+- Would be cute to dynamically change the information based on the calculator filter. i.e. when making a build for Aru, we should use the Aru unit names in the help information instead of Q'Rath
+
+
+---
+
+The TutorialHelperComponent should change it's information based on the selected Immortal and Faction.
+
+Currently, it explains a hard coded example of a user playing as Q'Rath and Orzum, and making a Legion Hall, Apostle of Bindings, a Soul Foundry, and 3 Absolvers and a Zentari.
+
+Obviously, if the the filter has Aru selected for the faction, the user would be making a Ether Maw, Altar of the Worthy, God Heart Upgrade and a Amber Womb.
+
+For the units, if they have the Immortal of Mala or Atlzan selected, they would be making Masked Hunters. But if they had Xol selected, they would instead be making Bone Stalkers.
+
+For the units, if they have the Immortal of Atlzan selected, they would be making Resinants. But if they had Mala or Xol selected, they would instead be making Blood Anchors.
+
+If they have Q'Rath selected, things are as they are. But if they have Ajari selected as the Immortal, they build Sipari instead of Zentari.
+
+The calculations should be based on the Alloy and Ether costs from the database.
+
+These variables will be need to be used, and will be taken from hard coded values on the page that matches the associated filter combinations.
+
+Given the steps can be very different between filter combinations, the exact contents will also need to be changed based on the filters. Note the extra God Heart Upgrade step for Aru.
+
+This hard coded content will need to be regenerated a a later date to match information currently in the database. But do not worry about implementing that right now.
+
+
+
+
+---

docs/Tasks/Highest Alloy and Ether Tests.md

@@ -0,0 +1,10 @@
+---
+type: Task
+status: Working On
+category:
+---
+![[Pasted image 20260601083206.png]]
+
+
+- Highest Ether should remain zero if ether is never built
+- Highest Alloy should be expected value

docs/Tasks/Hotkey Tests.md

@@ -0,0 +1,10 @@
+---
+type: Task
+status: TODO
+category:
+  - QA
+---
+![[Pasted image 20260601083101.png]]
+
+- Make sure each upgrade can only be researched once
+- Remove abilities from the Build Calculator, instead have a helper UI that shows researched upgrades and unlocked abilities

docs/Tasks/Improve your SEO.md

@@ -0,0 +1,11 @@
+---
+type: Task
+status: TODO
+category:
+---
+Maybe the default is already fine, given this website actually pops up if I type in "Immortal Gates of Pyre Database" or "IGP Database" but I should at least consider this as a topic.
+
+---
+
+
+Also add back in that www.subdomain stuff because google is looking at that url instead.

docs/Tasks/Input building delay should have an effect on when a building is built. Tests against 0, 2, 4, 60.md

@@ -0,0 +1,11 @@
+---
+type: Task
+status: TODO
+category:
+  - QA
+---
+
+![[Pasted image 20260601083030.png]]
+
+
+Input building delay should have an effect on when a building is built. Tests against 0, 2, 4, 60

docs/Tasks/Jenkins CI.md

@@ -0,0 +1,5 @@
+---
+type: Task
+status: TODO
+category:
+---

docs/Tasks/Language Support.md

@@ -0,0 +1,5 @@
+---
+type: Task
+status: Blocked Backlog
+category:
+---

docs/Tasks/Make Examples be based on Database Information.md

@@ -0,0 +1,4 @@
+---
+type: Task
+status: Backlog
+---

docs/Tasks/Make Tests for the Build Calculator.md

@@ -0,0 +1,49 @@
+---
+type: Task
+status: Done
+category:
+---
+
+Add an Acropolis with the Q key. Verify it was added to the EntityClickView and the Timeline component.
+
+Press the Clear Build Order button.
+
+Observe that the Acropolis is no longer displayed in the  EntityClickView and the Timeline component. 
+
+
+---
+
+Duplicate the 'Add entities via hotkeys TAB, Q, W, E with Q\'Rath/Orzum' test. But instead of clicking the hotkeys, use the matching keyboard inputs. i.e. Send the keyboard TAB key, instead of clicking on the UI component representing the TAB key.
+
+In order to make these keyboard key presses though, the HotKeyViewer component needs to be the Focused Element. So click it first before sending the key inputs. It only needs to be clicked once.
+
+
+---
+
+
+
+Past
+
+
+---
+
+Make the filter component have Faction: Q'Rath and Immortal: Orzum selected.
+
+Add every entity to the build calculator by click on the first four keys. TAB, Q, W, E. 
+
+After each action that would cause an entity to be built, check to see if the name on the key matches the name now display in the EntityClickViewComponent.
+
+Such as Apostle of Binding on the TAB key should show above.
+
+---
+
+
+On the build calculator page, click the grey out HotKeys. Ensure a Toast with the related error appears.
+
+Clicking on Soul Foundry without a Legion Hall should give the "Missing Requirements" error toast.
+
+---
+
+On the build calculator page, click the E hotkey for Soul Foundry. Ensure an error toast with "Not Enough Ether" appears.
+
+Clicking on Soul Foundry with a Legion Hall should give the "Not Enough Ether" error toast.

docs/Tasks/Make a Plan to Fully Test the Calculator.md

@@ -0,0 +1,103 @@
+---
+type: Task
+status: Done
+category:
+---
+
+![[Pasted image 20260601083019.png]]
+
+- Top border on the Options component changes based on the selected Faction. Light-gray-blue for Q'Rath, Red for Aru.
+- Top border on Entity Click View component changes based on the selected Immortal. Ex. Grey-ish-Green for Xol, Green-red for Mala, Brown for Atzlan. Dark-grey-ish-blue for Orzum, Light-ish-blue for Ajari.
+- Should clear out current build. Should show a warning dialog if your going to clear out your current build
+- Shouldn't show an error dialog if your not clearing out a build. Add a unit, then clear it out, before testing to ensure this works
+- 
+
+
+![[Pasted image 20260601083005.png]]
+
+- Fix bug where Entity View is not being cleared on clicking the Clear Build Order button
+
+
+![[Pasted image 20260601082954.png]]
+
+- Ensure build order gets greyed out past the attack time. Clicking the cancel button will wipe the entire greyed out timeline.
+
+
+![[Pasted image 20260601083030.png]]
+
+- Input building delay should have an effect on when a building is built. Tests against 0, 2, 4, 60
+- Ensure negative values cannot be used. Ensure an error toast appears telling you values cannot be negative.
+- Ensure Wait To time waits to the established time.
+- Ensure Wait To shows an error toast when waiting to an elapsed time.
+- Ensure Wait Time adds the waited time.
+- Ensure Wait Time cannot be negative.
+- Waits need to be shown in the Timeline Component
+
+
+![[Pasted image 20260601083046.png]]
+
+
+
+- Make sure the dialogs and sub dialogs work
+- Ensure the displayed unit changes when clicking on a different unit
+
+![[Pasted image 20260601083101.png]]
+
+- Make sure each upgrade can only be researched once
+- Remove abilities from the Build Calculator, instead have a helper UI that shows researched upgrades and unlocked abilities
+
+
+????
+
+- Add a timeline editor UI
+
+
+
+![[Pasted image 20260601083113.png]]
+
+Workers, update UI to
+
+- Mining
+- Building
+- Creating
+- Idle
+- Total
+
+Have the Alloy tooltip and Ether tooltip, show you where the ether is coming from. Also show greyed out items that are no longer producing resources. Same for supply. And Pyre.
+
+
+- Alloy Income should increase and decrease based on bases being built and mining out
+- A worker should show as busy when one becomes busy
+- A work should show as being created when one becomes created
+- Supply should increase when building buildings that provide supply.
+- Supply should decrease when canceling buildings that provide supply.
+- Should show static Pyre income
+- Pyre should increase at expected rate
+- 
+
+
+![[Pasted image 20260601083127.png]]
+
+
+- Attacking Time should be Travel time plus Completed At time.
+- Built units should show in the Army units built component
+
+![[Pasted image 20260601083147.png]]
+
+- Ensure starting text changes to match the filtered faction
+- Need to be able to clear items out from the timeline. This retriggers calculations. Show a warning dialog when you would delete a prerequisite and cause further items to be deleted. ie. Soul Foundry depends on Legion Hall, are you sure you want to remove Legion Hall and all required content.
+
+![[Pasted image 20260601083206.png]]
+
+
+- Highest Ether should remain zero if ether is never built
+- Highest Alloy should be expected value
+
+![[Pasted image 20260601093510.png]]
+
+- Split to be Total Alloy and Ether spent on raw Army Units
+
+![[Pasted image 20260601083333.png]]
+
+- Ensure referenced data is taken from the database.  Unit names and costs are currently hard coded.
+- Would be cute to dynamically change the information based on the calculator filter. i.e. when making a build for Aru, we should use the Aru unit names in the help information instead of Q'Rath

docs/Tasks/Make page object pattern structure for the Build Calculator and all it's components.md

@@ -0,0 +1,13 @@
+---
+type: Task
+status: Done
+category:
+---
+Make page object pattern structure for the Build Calculator and all it's components.
+
+I am referring to the build calculator found here: IGP\Pages\BuildCalculator\BuildCalculatorPage.razor. Save the page object patter structure here: Playwright/pages
+
+Each of it's components should be in a sub folder called buildCalculator.
+
+This will be used later to make new playwright tests.
+

docs/Tasks/More Wait Tests.md

@@ -0,0 +1,15 @@
+---
+type: Task
+status: TODO
+category:
+  - QA
+---
+![[Pasted image 20260601083030.png]]
+
+
+- Ensure negative values cannot be used. Ensure an error toast appears telling you values cannot be negative.
+- Ensure Wait To time waits to the established time.
+- Ensure Wait To shows an error toast when waiting to an elapsed time.
+- Ensure Wait Time adds the waited time.
+- Ensure Wait Time cannot be negative.
+- Waits need to be shown in the Timeline Component

docs/Tasks/Nice looking map refrence.md

@@ -0,0 +1,5 @@
+---
+type: Task
+status: Blocked Backlog
+category:
+---

docs/Tasks/Plan Calculator.md

@@ -0,0 +1,4 @@
+---
+type: Task
+status: Backlog
+---

docs/Tasks/Remove Items from anywhere in the build calc timeline.md

@@ -0,0 +1,5 @@
+---
+type: Task
+status: Backlog
+category:
+---

docs/Tasks/Spells are currently a production item in data. Make the a ability item so they don't show under production table.md

@@ -0,0 +1,5 @@
+---
+type: Task
+status: Backlog
+category: Bug
+---

docs/Tasks/Timeline Tests.md

@@ -0,0 +1,9 @@
+---
+type: Task
+status: TODO
+category:
+---
+![[Pasted image 20260601083147.png]]
+
+- Ensure starting text changes to match the filtered faction
+- Need to be able to clear items out from the timeline. This retriggers calculations. Show a warning dialog when you would delete a prerequisite and cause further items to be deleted. ie. Soul Foundry depends on Legion Hall, are you sure you want to remove Legion Hall and all required content.

docs/Tasks/Top Borders in Calculator should change based on Selected Faction and Immortal.md

@@ -0,0 +1,28 @@
+---
+type: Task
+status: AI Agent Work
+category:
+  - Feature
+  - QA
+---
+![[Pasted image 20260601083019.png]]
+
+- Top border on the Options component changes based on the selected Faction. Light-gray-blue for Q'Rath, Red for Aru.
+- Top border on Entity Click View component changes based on the selected Immortal. Ex. Grey-ish-Green for Xol, Green-red for Mala, Brown for Atzlan. Dark-grey-ish-blue for Orzum, Light-ish-blue for Ajari.
+
+---
+
+Make two new UI component to handle the border display changes based on events given by the FilterService.
+
+One will listen against events on the GetFaction changes, and one based on the GetImmortal changes.
+
+These new UI components will be layered on top of FormLayoutComponent. 
+
+The purpose is to change the top border colour based on events, to act as UI feedback.
+
+One component will cover the FilterComponent for changing the Faction, and one component will cover the EntityClickViewComponent for changing the Immortal.
+
+Goal is to accomplish:
+
+- Top border over the FilterComponent component changes based on the selected Faction. Light-gray-blue for Q'Rath, Red for Aru.
+- Top border on EntityClickViewComponent changes based on the selected Immortal. Ex. Grey-ish-Green for Xol, Green-red for Mala, Brown for Atzlan. Dark-grey-ish-blue for Orzum, Light-ish-blue for Ajari.

docs/Tasks/Update the Reference Tables with Telerik.md

@@ -0,0 +1,4 @@
+---
+type: Task
+status: Backlog
+---

docs/Tasks/WebAssembly back to Azure.md

@@ -0,0 +1,5 @@
+---
+type: Task
+status: Backlog
+category:
+---

docs/Tasks/Worker Income UI and Tests.md

@@ -0,0 +1,26 @@
+---
+type: Task
+status: TODO
+category:
+---
+![[Pasted image 20260601083113.png]]
+
+
+Workers, update UI to
+
+- Mining
+- Building
+- Creating
+- Idle
+- Total
+
+Have the Alloy tooltip and Ether tooltip, show you where the ether is coming from. Also show greyed out items that are no longer producing resources. Same for supply. And Pyre.
+
+
+- Alloy Income should increase and decrease based on bases being built and mining out
+- A worker should show as busy when one becomes busy
+- A work should show as being created when one becomes created
+- Supply should increase when building buildings that provide supply.
+- Supply should decrease when canceling buildings that provide supply.
+- Should show static Pyre income
+- Pyre should increase at expected rate