yecats / dotgame Goto Github PK

Adding based on a few questions that I've had e-mailed to the .GAME alias.

Adding this based off of a request sent to the .GAME e-mail alias.

• The difference between an Animator and Animation and how you initially create both when trying to add an animation.
• Creating animations without sprite sheets
  • A single sprite or even a game object made of multiple sprites
• Creating animations with sprite sheets
  • how to create a sprite sheet
  • Suggestions when creating sprites
• Transitions
  • Personally I felt these were fairly easy, but it lead me to the next point.
  • Do you need to animate every "state" of an object?
    • If the object does not do anything when it is idle do you need to create an animation where nothing changes to act as the default state?
• Adding animations to a controller
• Reusing animations

Hey there!

Just watched the first .GAME episode (congrats btw 🙂) and was wondering if there was any chance to see the Duality game engine covered as a topic someday? We're on GitHub too and it's basically an MIT-licensed 2D-only engine / editor combo, written in 100% managed C# code. There's a small community around it and we'e actively looking for contributors to help us carry the project into the future.

You can find most information on the info page above, but if you prefer a less involved perspective, there is also a Closer Look at the Duality Game Engine video from he Gamefromscratch blog.

Reasons not to cover Duality

• Duality doesn't have nearly as much momentum as, for example, Unity. Even mentioning both engines in the same sentence regarding momentum appears ridiculous.
• It doesn't bring all the features people might expect and it's nowhere near the same state of multi-platform support as the big engines.
• There isn't really much business happening around Duality.
• Being Open Source and driven forward by people in their free time, there is far, far less energy available to drive the development forward, so it's not really playing in the same league at all.

Reasons to cover Duality

• Duality is not something most people already know about. It's new and interesting, and certainly something that the big majority of indie and hobby game developers haven't had the chance to consider trying. It's some fresh air in a world where Unity is considered the obvious choice.
• It's built on top of the .Net ecosystem directly and embraces what's already there, with user code just being a .Net Assembly and package management based on NuGet. C# is not a scripting language it uses, but its very own foundation.
• MIT-licensed with no strings attached, making it a good choice in situations where usage restrictions or licensing costs can be an issue.
• Duality promotes ownership and custom-built solutions over putting together pre-made parts by providing an open plugin-based architecture and API endpoints to tie into.

Ideas on how to cover Duality

• Adding it to the README list of game engine resources.
• Featuring it in an "first look at" episode on the show, among other presented options. (Let me know if I can help with resources or input.)
• A short, one-episode "and now for something completely different" tutorial somewhere inbetween, with the audience primed as this not being a fully backed recommendation, but more of a "Hey, let's look at this obscure thing together" video. (We're not Unity. Better to start humble.)
• Others?

Let me know what you think, and feel free to be brutally honest. 🙂 If you have any questions, I'll try to help where I can.

Porting this request over from Reddit.