Nez VS MonoGame.Extended

I'm developing an RPG in C# using MonoGame and the Nez game engine. Looking for hobbyists who would like something to do in their free-time and/or one programmer and one pixel-artist. Below is a link to a Google Drive folder w/ information regarding the game's design. Any comments, suggestions or otherwise are also welcome!

Monogame has a good number of libraries, ranging from utility and QOL stuff all the way up to something like Nez, a huge library completely reworks how Monogame works.

I have an entity-based component system based on Nez that implements most of the lower level functionality of my game, such as animation, rendering, physics, and collision initiated interactions. It was originally supposed to be an ECS but now I consider it more of an entity-based component system since the components are more about adding functionality to entities, rather than data and there (currently) are no separate systems. I've implemented a custom messaging system, of which I am quite proud, so that when one component needs to send a message to another component it doesn't have to perform a lookup using reflection nor does it need to always store a reference to that component.

They still have an Entity-Component system, but no longer an Entity-Component-System system. The part of the FAQ I’m referring to is here: Entity Systems

If your background is in C#, and you think Unity is overkill or you don't want to be taken out of a pure code ecosystem (unity is like a glorified level editor), then I would highly recommend MonoGame using the Nez framework https://github.com/prime31/Nez . Its all C#, and it gives you everything you need to start making a game and nothing else - just the kitchen sink. It gives you a game loop, media capabilities, an actor system, a UI system, collisions, animation tweening, and a lot more. The code to get started is literally simpler than a new WPF app. Check out the sample library. https://github.com/prime31/Nez-Samples The code to create a 2d tileset game with collisions, a follow camera, and a movable character who can shoot fireballs is only 300 lines long.

Here's an example of a more fleshed out game engine built for monogame: https://github.com/prime31/Nez

If you're cool with just writing code with no GUI environment, I'm a big fan of Monogame, especially when paired with the Nez library extension. Using Monogame by itself is fine and let's you do basically everything from scratch how you want it, but Nez gives you a strong foundation of basics handled for you without completely getting in your way, including an entity-component style workflow that you may be used to from Unity.

MG.Extended.Tiled serialization is just XML, if you know how to deserialize XML, you can just read in your maps using System.Xml

MLEM is a library for monogame that has spritesheets and animations. As well as Monogame.Extended. Both open source libraries you can look at for inspiration, or use if you don't want to write your own.

Monogame has a good number of libraries, ranging from utility and QOL stuff all the way up to something like Nez, a huge library completely reworks how Monogame works.

Here are your draw methods for monogame extended sprite https://github.com/craftworkgames/MonoGame.Extended/blob/a3373ac26d90c9801b71b55679f1199fa4ec22a6/src/cs/MonoGame.Extended/Sprites/SpriteExtensions.cs

It seems to have the ability to draw geometry (and much more -> https://github.com/craftworkgames/MonoGame.Extended/blob/develop/src/cs/MonoGame.Extended/Math/ShapeExtensions.cs