rust-adventure / bevy-snake Goto Github PK

Code and workshop lessons should both be updated.

https://bevyengine.org/news/bevy-0-13/

Relevant Bevy Changes (that have to be dealt with)

• TextureAtlas has been reworked
• Some changes to how long events live when dealing with FixedUpdates.

Relevant Bevy Changes (that could make the workshop better)

• 9-slice scaling is built-in now. It would be nice to re-introduce 9-slice scaling based UI elements. This was removed when the workshop moved away from kayak-ui in an earlier revision.
• one-shot systems have had restrictions lifted. Is a one-shot system better than the apple event reading system for spawning apples?
• Gizmos are getting better and better, is there an opportunity to take advantage of gizmos before introducing sprites?

System Stepping

System Stepping was introduced in 0.13. This is very interesting in general, as it allows controlled progress in a game allowing debugging system effects visually on a one-by-one debugger level.

Potential drawbacks:

• At the moment, events may not be read correctly in stepped systems. This is something used for apple spawning, so apple spawning would likely have to be excluded from system stepping and this would have to be mentioned.
• Similarly, conditional systems have the same restriction
• Snake is already quite a long workshop, so its possible this shouldn't be added here and instead introduced in a different workshop.

Bevy 0.14 is out. Code for Snake needs to be updated.

Anticipated changes include:

• Observers for apple spawning, etc.
• Removal of FixedTimestep in favor of timers
  • This matches what is happening to the Bevy official examples, which deprioritize FixedTimestep and look like it is going to go behind a flag soon.
• Some color changes
• There's more Rand support in Bevy, is any of it useful?

---

• Should the character selection screens (and other menus) be removed?
  • It seems like "UI" isn't what people are most interested in when going through these workshops, and UI can always be pushed out to another, smaller, workshop.
  • this would make the workshop significantly smaller because all UI and related functionality would be removed. This makes it both easier to update from my end, and faster to get through from a learner's end.