Project Part 1.

• I am watching this video
  • These notes are from the start to 49:45. (Through Player Flipbooks).
• Note : "Clean Structured maintainable blueprint code"
• Components
  • Flip Book Animation.
  • Tile Sets and Tile Maps.
• Start out with an empty project, no assets.
• When setting thing up (First 10-15 min)
  • He sets up a standard file structure.
    • You may wish, for group work, to add a user level under these.
  • He mentions the "coding standards"
    • I can't emphasize this enough.
    • You were introduced to a "style guide" in 130/230/330
    • In included naming conventions and usage.
    • You should not abandon this now.
  • You can form your own style, but I would follow
    • The standard from the videos you are watching.
    • this style guide
    • Or a modified version of the above.
  • This includes
    • Naming assets, programs, ...
    • Note when he makes directories he follows the Asset Naming Conventions.
  • As a group, I would discuss this.
    • Nothing is worse than trying to cram everything together at the last minute and not being able to find anything.
    • Or having to recreate work because the entire structure is so bad you can't find what you need.
• The game mode
  • See the Unreal Documentation.
  • This is part of a design that holds the global game information.
    • This is not really required, but it is the standard.
• Note that this system is very much an object hierarchy.
  • Keep this in mind when you work.
• I have always found the search bars to be life savers
  • Watch how he uses them.
  • Take advantage of them.
• The first 20 min or so are strictly setup.
  • If I were in this long term, I would make some notes on how to do specific things.
    • Like set up input.
    • And project settings.
      • There are so many of these I find them overwhelming.
      • So some quick notes in a searchable format would be great.
• Notice he keeps things organized and small
  • Ie, when he deals with his input, he adds that to a new event graph called input.
  • Also notice he sets up comments, even on simple functions.
  • Also notice that he is somewhat pedantic about his alignment.
  • 
• It took me a while to find his assets, they are Here
  • Root directory
• What now.
  • You should watch at least this much of the video.
  • You should gather as a team and start working on a design.
    • You will need a story.
    • You should pick a theme
    • You should decide on the player and the NPCs
    • Decide what movements you want your NPC's to do.
    • I would have each team member create a NPC with the different animations.