Search Results
6/15/2025, 11:42:21 AM
>>105599397
Monogame itself is relatively decent (okay support for x-platform and portability across consoles) but it holds onto a lot bloated concepts and XNA legacy, holding it back. Some decent indies have been created with MG, but the content pipeline really sucks to work with, as mentioned.
FNA is even more legacy, trying to be a pure re-implementation of XNA 4 (15 year old as this point) and nothing else.
There's also shit like MonoGame Extended and Nez, which sit on top of MG, but I found buggy, bloated and/or lacking documentation.
Honestly for 2d games you're better off creating a specialized engine yourself using SDL2-CS, SFML.Net or Raylib-cs. It's not that complicated if you know what you need. Take a look at MG(E)/Nez source and yoink what you need if you cba to reinvent the wheel. All are on NuGet and come without the bloat that MG (or even Java shit like libGDX) comes with.
Monogame itself is relatively decent (okay support for x-platform and portability across consoles) but it holds onto a lot bloated concepts and XNA legacy, holding it back. Some decent indies have been created with MG, but the content pipeline really sucks to work with, as mentioned.
FNA is even more legacy, trying to be a pure re-implementation of XNA 4 (15 year old as this point) and nothing else.
There's also shit like MonoGame Extended and Nez, which sit on top of MG, but I found buggy, bloated and/or lacking documentation.
Honestly for 2d games you're better off creating a specialized engine yourself using SDL2-CS, SFML.Net or Raylib-cs. It's not that complicated if you know what you need. Take a look at MG(E)/Nez source and yoink what you need if you cba to reinvent the wheel. All are on NuGet and come without the bloat that MG (or even Java shit like libGDX) comes with.
Page 1