supercilex / grocery_bagger_9000 Goto Github PK

• Change the color of placed pieces according to their score
• Add a meter below bags that shows score or num blocks placed
• Show +num_points every time you place a piece

And maybe adjust max cumulative ttl.

• "Candy" which is a single block to help players patch up holes. Could be doled out for doing well or maybe if the player is doing poorly. Case could be made for either. From the original doc:
  • Candy is awarded after a bag is completed.
  • Candy is unlocked with multipliers as player fills bag
  • Candy is 1x1 piece
  • Candy is rainbow, counts for any color, but not as additional colors
• Power ups. You can have N of a certain power up at a time. Every M seconds you receive a power up. Power ups have a cooldown timer so they cannot be stacked (that is, you can’t use two slow times right away). If a power up lasts for X seconds, then the cooldown timer is X+Y seconds.
  • Slow time
  • Piece any piece from the conveyor belt (instead of just the front 3)
• Trash/broken items. Some items could be grayed out (to mean they are bad) and need to be placed in a trash can or you lose a ton of points.
• Express lane as a breather from longer levels with just one bag and one color.

Export level files and load them at runtime (probably baked into the binary though because web makes a request per asset and we don't want playability to be dependent on internet connection).

Stuff the files would contain:

• Conveyor belt pieces
• Robot
• Bags

Only lets you select levels you've already completed.

Maybe wait until mouse outside bag? Animate piece to mouse. Needs the same resume support as #15.

• https://bevyengine.org/learn/book/migration-guides/0.7-0.8/
• https://bevyengine.org/news/bevy-0-8/#query-intoiter
• https://bevyengine.org/news/bevy-0-8/#query-iter-many
• https://bevyengine.org/news/bevy-0-8/#convert-mutable-queries-to-read-only
• https://bevyengine.org/news/bevy-0-8/#time-to-prepare-and-compute-schedule-with-100-systems-in-milliseconds-less-is-better
• https://bevyengine.org/news/bevy-0-8/#hierarchy-commands
• https://github.com/jakobhellermann/bevy-inspector-egui#custom-components-in-the-world-inspector
• Use scenes for config?
• https://bevyengine.org/news/bevy-0-9/#improved-entity-component-apis
• https://bevyengine.org/news/bevy-0-9/#system-ambiguity-resolution-api-improvements
• https://bevyengine.org/news/bevy-0-9/#camera-viewport-to-world
• https://bevyengine.org/news/bevy-0-9/#plugin-settings
• https://bevyengine.org/news/bevy-0-9/#hierarchy-query-methods
• https://bevyengine.org/learn/book/migration-guides/0.8-0.9/
• https://bevyengine.org/news/bevy-0-10/#const-bevy-ui-defaults
• https://bevyengine.org/learn/book/migration-guides/0.9-0.10/

• bevyengine/bevy#4879
• bevyengine/bevy#3253
• bevyengine/bevy#4692

https://github.com/rust-unofficial/awesome-rust#games

Original idea:

• Left/right, A/D, Z/C to change the highlighted piece
• Space, Enter to select the piece
• It now appears above the center-left bag
• ShiftA/ShiftD, ShiftQ/ShiftE to change bags
• A/D, Left/Right to move the piece above a bag (and go to the next bag on wrap around)
• Q/E to rotate piece
• W/S, Up/Down to shift pieces into slots
• Enter/Space to place piece
• Esc to back up one step

People want this, but I have no idea how it interacts with the robot: the issue is that you can place a piece, the robot places on top of you, and now you undo which leaves a floating piece. Or we disallow undo after robot placement, but that feels inconsistent.

• Doing everything at compile-time ensures everyone has the same experience.
• Use a sliding shuffle for piece ordering. This makes sure pieces stay relatively close where they started so the level is easier to solve.
• Use code to generate human readable and machine readable configs. The human readable format should probably use RON while the machine readable one should be bincode. Load machine configs for game as include file. Add golden test that verifies configs were generated from code. Include the seed in the config so it can be re-generated.
• This would be a binary you run that has config as code and generates the persisted configs that are loaded in the game.
• A bag of pieces would be selected from the set of all possible fillings.
• See if bit manipulation can be used for the tetris solution finder (bag filling finder) instead of array accesses. Also check dancing links paper to see if they already solved this problem.

Squish/spring/squelch

Robot + web analytics.

Probs needs component that stores active bags.

So it doesn't overlap the score juice.

Upon clicking restart 2 times, highlight the piece you're supposed to select and add outlined piece that shows desired rotation.