Mobile Eggbert

Mobile Eggbert
Release date (C#)	25th November 2024
Release date (C++)	Not yet
Github (C++)	https://github.com/openeggbert/mobile-eggbert
Github (C# Core)	https://github.com/openeggbert/mobile-eggbert-core
Github (C# MonoGame Android)	https://github.com/openeggbert/mobile-eggbert-monogame-android
Github (C# MonoGame Desktop)	https://github.com/openeggbert/mobile-eggbert-monogame-desktop
Github (C# FNA Desktop)	https://github.com/openeggbert/mobile-eggbert-fna-desktop
Github (C# KNI Web)	https://github.com/openeggbert/mobile-eggbert-kni-web
Programming languages	C#, C++
Game frameworks	MonoGame, FNA, KNI, CNA, XNA 4.0, SDL 3

Mobile Eggbert is a 2D platformer game based on Speedy Blupi for Windows Phone.
The ILSpy decompiler was used to get back the C Sharp|C# source code of Speedy Blupi for Windows Phone. The decompiled source code is not the same, as the original was. Comments and names of local variables are lost.
The discontinued XNA 4 game framework is replaced by MonoGame game framework. MonoGame is almost a drop-in replacement for the XNA. There are several implementations of XNA 4.0 game framework (like FNA or others).
See also: Alternative implementations of XNA
Work on Mobile Eggbert started on 23rd November 2024.
Already on 23rd November 2024 the game was successfully decompiled and made runnable without any errors on desktop (Windows and Linux). The support for mouse and keyboard was added.
On 25th November Mobile Eggbert was released for Windows and Linux: https://drive.openeggbert.com/Mobile_Eggbert/

It works without any issues.

Why Mobile Eggbert was created

Mobile Eggbert was started, because:

Windows Phone is a discontinued closed-source proprietary mobile operating system (developed by Microsoft company for smart phones).
Devices with Windows Phones are no more produced. Windows Phone operating system cannot be installed on other modern devices.
Without physical device with Windows Phone installed the emulator is the only way to run Speedy Blupi (2013) nowdays. But the emulator probably will not work in the future, as it is a closed-source proprietary technology.
Because the source code of Speedy Blupi (2013) is not available, it is not possible to make improvements or bug fixes.

Current status

Mobile Eggbert works on Windows and Linux.
Mobile Eggbert starts on Android, but it is buggy: scaling is wrong, touch controls are not working correctly, worlds are not loading.

Issues and the future

Mobile Eggbert is buggy on Android and must be fixed.
Accelerometer support is not yet available. It will be added for the Android platform.
Local variables must be renamed to the correct names.
Comments must be added.
Some refactoring is planned.
Porting to FNA or an alternative XNA 4.0 is planned to be done.
If the C# version will be kept, then there will be probably 3 modules: mobile-eggbert-core, mobile-eggbert-desktop and mobile-eggbert-android.
Mobile Eggbert is being just rewritten to C++. MonoGame is replaced by CNA.

Reasons to Rewrite Mobile Eggbert in C++ and CNA

Performance Gains – C++ allows for more efficient memory management and CPU usage, improving the game's responsiveness.
Direct Hardware Access – CNA (built on SDL 3) provides direct access to graphics, input, and sound hardware, leading to better optimization.
Cross-Platform Compatibility – SDL-based frameworks ensure support across Windows, Linux, and macOS without relying on .NET.
Future-Proofing – XNA has been deprecated, and MonoGame is tied to .NET, which evolves frequently. C++ offers long-term stability.
Console Support – SDL-based frameworks are commonly used for developing console games.
Better Dependency Management – C++ eliminates .NET version dependency issues encountered with MonoGame.

Reasons not to Rewrite Mobile Eggbert in C++ and CNA

Development Complexity – C++ requires manual memory management and has a steeper learning curve compared to C#.
Less Built-in Features – CNA may require more custom coding for engine components that MonoGame provides natively.
Longer Development Time – Transitioning to C++ might take longer due to lower-level coding requirements.