🐬❄️ ↝ Performing a review of tickets in progress -> p1

content/Projects/Star Sailors Frontend/V2 Routes Tasks.md

@@ -1,68 +1,35 @@
-# Planets
-1. I think that all structures on a planet's sectors will be accessible from the planet page, eventually. For now, this is going to cause all sorts of issues, so let's hold off on this for now.
-2. How does tree data affect what's going on here?2
+# Components to design
+### Planet views
+1. Ring layout
+	* Could be used to display structures in orbit
+	* This is dependant on the classification models that will be available in V2.0, potentially we won't need to launch anything into space and therefore we can hold off on this for now.
 
-### Ring/layout
-1. Currently the ring layout just has the base images for items in the inventory, no functionality in terms of assuring the planet/sector has those items
-	1. I'm going to create a function to go through a planet and see all the items/structures in the sector, and vice versa
-## Sectors
-* Generated bg images/maps for each sector route
-* Generate complete make-up/composition when creating a new sector, including confirming that the rover images change each time
-
-## Data
-* Need to get planet data to filter into sector data - currently it's all disorganised see ![[Pasted image 20240415133401.png]]
+### Sector views
+Sectors won't be pages, they'll be individual overlays, I think starting off as a popup list that shows the basic information. The interactions in-game are occurring on a planet-scale for now (e.g. deploying rovers, building/interacting with structures) so I don't think we need to have any write-actions for sectors at the moment
 
-# Explore
-* Sector route -> [[Explore.tsx]] 
-* Fix background image issue on `/explore/[id].tsx` route
+* Background images & maps/portions of maps could be useful though
+* Generate complete make-up/composition when creating a new sector, including confirming that the rover images change each time
 
-# Index
-* I think we'll show the user's spaceships, automations, and planet charicatures on the index route. At the bottom we'll have the navigation area, which will allow for the accordions to be selected
-* .limit(3); // Set this to be owned planets -> for planet gallery card/garden
-* It appears now that the sectors can be visited from the dashboard (i.e. the deeplinks work!)
-* Perhaps we could show a grouping of public sectors underneath the accordion area?\
-		* I'm having a go at experimenting with what could go below the accordions, currently we've got the sectors & inventory working. Defeats the purpose of the accordions, but while they've been a good stopgap at helping me/us figure out what needs to be shown, I think (thanks to [@Rhys Campbell](https://signalkineticsgroup.slack.com/team/U05MVAXPMCL)) that we've possibly found a better way.  
+### Media
 * Could the bg image be made up of a representation of your colony? "Our space colony".mp3
-* ![[Pasted image 20240416171347.png]]
 
-* The onboarding area/index page could house a bento box until we get the user comfortable with the VP-minimal UI
-* Bento box -> your planet, your vehicle, citizen module, mission list, inventory
-* Possibly we could have an option to toggle the bentogrid component, or highlight the missions. Determining if this is a feasible compromise and when/how to execute/introduce this will be a decision for Rhys
-* Another big error -> too many components on the page causes the scroll to go past background/cover image.
-* Or could your "home page" just be an interactable home base with a menu? So essentially take `/planets/{[your]id}` and move that to index route?
-
-# Collecting resources
-* "Old crypto interface" -> we've now decided to implement a collection system based on time since/of deployment. This will suffice for V2.0 until we can implement a more robust game language
-* I've got some new ideas for a responsive control panel that I've shared on `SGV2-7` ticket. The key thing here is that we keep some traditional vehicle controls.
-	* **Put everything into a bento grid.**
-	* **We could have a side-scrolling section that shows all the information/context**
-	* **Control panel/control(ler)s, camera, and then data/information**
+## Data
+* Need to get planet data to filter into sector data - currently it's all disorganised
 
+# Bugs
+### Supabase
 * Error: using the `AddResourceToInventory` button on `planets/sector/{$id}` does NOT add a sector value. I am assuming this is a bug as we do have a discriminator in the component definition, and not that this is intended to be the case (e.g. structures will be confined to a sector/planet, while items may not be by default? But should they at least show where they originate from)
-	* This is relevant if we don't create these components again from scratch (for clarity, I am advocating for taking as much as possible from `initialClassification` branch/`SGV2-10-...` before the new project defined in `SGV2-24`)
 
-![[Pasted image 20240419172514.png]]
+# Items
+### Automatons
+Each of these will be introduced in the `inventoryITEMS` table, and they will have a parent item of id: `22`, as this is the "Vehicle launch structure". Not all of these will be vehicles, however for now we are working on rovers so this is the best way to do it for now
+
+* Rovers will start on a planet and then be deployed (multiple times) to a sector to explore (gain information), collect resources, aide in construction, or collect info to review (e.g. photos). > SGV2-20 
+* * SGV2-20: I will set rovers to be craftable using 1 piece of iron, this will be a placeholder crafting recipe (see [[Crafting]]) and will not use the crafting microservice/API route during this phase of development. Items will be collected just by the rover, there won’t be any special modifications/'rover arms' etc. for now.
 
 # Classifications
-* I think we should move everything into a single `classifications` table, have a single table for everything that is going to be catalogued, and then differentiate between them in the same way we have a single table for every item type. I will review this with Dave.
+### Rover data
 * Each sector has a series (currently one, could be multiple though) of images from a rover, which can be classified (and would then return a reward, theoretically allowing us to structure the inventory/items component into this)
-
-# Structures
-* I just realised that the telescope selector doesn't require the telescope to exist on the planet (afaik at the moment)
-	* We have done this successfully for the sectors/{$id} route, though, which is good.
-
-Going forward, while in this current testing sprint, all entries into `inventoryUSERS` will go into `planetId = 2`, `sectorId = 18` if being created for my user profile.
-
-### Rovers/Automatons
-Each of these will be introduced in the `inventoryITEMS` table, and they will have a parent item of id: `22`, as this is the "Vehicle launch structure". Not all of these will be vehicles, however for now we are working on rovers so this is the best way to do it for now.
-
-* SGV2-20: Rovers will start on a planet, and then migrate to a sector. As sectors are no longer "explorable" via the frontend
-
-* SGV2-20: I will set rovers to be craftable using 1 piece of iron, this will be a placeholder crafting recipe (see [[Crafting]]) and will not use the crafting microservice/API route during this phase of development. Items will be collected just by the rover, there won’t be any special modifications/'rover arms' etc. for now.
-# Hosting
-* We'll host all the flask API(s) on a few raspberry Pis, thanks to Rhys
-
-
 # Review (4-7/5/2024)
 I would say the goals are as follows for V2:
 1. Voidpet interface, supporting all below features