Flicky 8: Relive Classic Sonic Mania with an Open-Source Engine

Recommended Related Projects and Games

If you’re exploring unique and intriguing projects or looking to dive into some captivating games, here are a few recommendations:

Horror and Creepypasta Stories

1. The Purple Truth by methamphetabear

• Engage with a mysterious and thrilling tale that keeps you on the edge of your seat.

2. Tragic Legacy: A Sonic Creepypasta

• Explore the complete story behind this eerie and fascinating creepypasta. 

3. Sonic.EXE: Classic Story

• Dive into the classic narrative that has haunted fans for years.

4. Mario.EXE: Oldum77 Edition

• Experience a chilling twist on the familiar Mario universe with this fan-made horror story.

Fan-Made Adventures and Nostalgia

1. Sonic Robo-Blast! From The Past

• Relive the past with this fan-created homage to classic Sonic games.

2. Creamy & SunFIRE’s Adventures

• Enjoy a fun and adventurous storyline featuring original characters in a familiar world.

Other Noteworthy Recommendations

1. Sonic, I HATE YOU! by YagoFranca

• Dive into an intense narrative packed with emotional twists and turns.

By exploring these projects and games, you’ll be sure to find a mix of nostalgia, horror, and adventure that will keep you entertained for hours. 

Who to Contact for Support with the Flicky Engine

For any issues or questions regarding the Flicky Engine, support is available directly from the developer. Reach out to them on Discord:

• Username: John-Kun
• Discord Tag: #4268

Feel free to message them with any technical difficulties or inquiries you may have. 

How to Fix Common Errors in Flicky Engine

Experiencing issues with Flicky Engine in GameMaker Studio 2? Here are solutions for some commonly encountered errors.

Error 1: Variable Not Set Before Reading

This issue often arises when the game attempts to play a sound that hasn’t been properly initialized.

Error Message:

Variable obj_game_over.SFX(100650, -2147483648) not set before reading it. At gml_Object_obj_game_over_Create_0 (line 8)

Solution:

1. Check Initialization:
   Ensure that your obj_game_over object correctly initializes the SFX variable.
2. Initialization Example:

// In the obj_game_over Create Event
SFX = { Jingle_GameOver: audio_get_id("Jingle_GameOver") };

3. Play Sound Safely:
Always verify that the sound exists before trying to play it.

if (SFX.Jingle_GameOver)
    PlaySound(SFX.Jingle_GameOver, global.SFXVolume, 1, 1);

Error 2: Incorrect Argument Type for audio_sound_gain

This error typically occurs when an argument expected to be of a number type is provided as a string.

Error Message:

audio_sound_gain argument 1 incorrect type (string) expecting a Number (YYGI32) at gml_Object_obj_audio_manager_Step_0 (line 33)

Solution:

1. Verify Argument Types:
   Check the arguments you’re passing to audio_sound_gain. The first argument (sound ID) must be a number.
2. Correct Usage Example:

audio_sound_gain(global.ZoneBGM, global.BGMVolume, 0);

3. Ensure Variable Types:
Make sure ZoneBGM is defined as a valid sound ID number.

global.ZoneBGM = audio_get_id("ZoneBackgroundMusic");

Error 3: Unknown Function or Script

This error happens when the game engine cannot find a function or script that’s being called.

Error Message:

Unknown function or script: caster_play at line 10

Solution:

1. Check Script Name:
   Verify the name of the script or function you’re calling. Typographical errors are common here.
2. Rename Usage Example:
   If the script is actually named caster_play_sound, adjust your code:

caster_play_sound(argument0, argument1, argument2);

3. Script Existence:
Ensure that the caster_play_sound script exists in your project and is properly defined.

4. Function Definition:
If missing, define the function:

/// @description Play a caster sound
function caster_play_sound(id, volume, loop) {
    audio_play_sound(id, volume, loop);
} 

By following these steps, you should be able to resolve the common errors encountered in Flicky Engine. Adjust the solutions to fit the specifics of your project if necessary. 

Common Errors When Using the Flicky Engine in GameMaker Studio 2

When integrating the Flicky Engine into GameMaker Studio 2 (GMS2), users often encounter several common issues. Understanding these errors can help troubleshoot and streamline your game development process.

Game Over Functionality

One frequent problem is the malfunction of the Game Over screen. Many users report that instead of ending the game and presenting the Game Over screen, an error log appears. This typically involves:

• Syntax Errors: Ensure that all your game over scripts are correctly written. Even a small typo can cause significant issues.
• Missing Assets: Verify that all necessary assets, such as images or sound files for the Game Over screen, are correctly loaded and referenced in your project.
• Broken Links: Double-check that all links to scripts, objects, or resources are functioning correctly.

Error Logs

Error logs may pop up, which can be daunting. However, these logs are crucial for diagnosing what went wrong. Common error messages include:

1. Null Reference Exceptions: These occur when the engine tries to access a variable or object that hasn’t been initialized.
2. Out of Bounds Errors: These happen when a script tries to access an array index that doesn’t exist.
3. Unexpected End of Script: This occurs if a script unexpectedly ends due to missing brackets, parentheses, or semicolons.

Performance Issues

Performance drops are another issue to watch out for. These can stem from:

• Memory Leaks: Ensure that you properly clean up objects and instances that are no longer needed.
• Heavy Scripts: Optimize scripts to reduce their load on the game engine.
• Resource Management: Loading too many assets at once can bog down the system, so consider loading assets dynamically as needed.

Compatibility

Lastly, ensure that the Flicky Engine version is compatible with your GMS2 version. Incompatibility issues can lead to unpredicted behavior or crashes.

By being aware of these common errors and how to address them, you can create a smoother development process and a more stable game. 

System Requirements for Running the Flicky Engine

To run the Flicky Engine smoothly, you’ll need to have certain versions of the Game Maker software installed. Here’s a quick rundown:

• Supported Versions:
• Game Maker 8.x: Ensure you have any version from the 8.x series.
• Game Maker Studio 14.x: Any version in the 14.x series will work.
• Game Maker Studio 2: The latest iteration is fully compatible with the engine.

Key Points to Remember

• Software Compatibility: Make sure your Game Maker software is up to date within the specified versions.
• Installation: Having the correct version installed before attempting to run the Flicky Engine can prevent compatibility issues and ensure a smoother experience.

By meeting these system requirements, you can take full advantage of the features and capabilities offered by the Flicky Engine. 

Specific Bug Fixes and Updates to the Flicky Engine

The Flicky Engine has received a comprehensive update, addressing several bugs and introducing new features to enhance gameplay and performance. Here are the key fixes and updates:

1. Palette and Transform Fixes

• Adjusted Super/Hyper palette changes for compatibility with Game Maker 8.x.
• Repaired Hyper Sonic transformation mechanics to ensure smoother transitions.
• Implemented fixes for Super/Hyper transformation sequences, providing more reliable functionality.

2. Character-Specific Improvements

• Resolved issues with Knuckles‘ glide functionality, ensuring accurate performance.
• Corrected Knuckles‘ rail animation for more fluid movements.

3. General Bug Fixes

• Conducted numerous bug fixes to enhance overall gameplay stability and user experience.
• Improved checkpoint system by adding more stars for better tracking.

4. Updates and Deletions

• Released Flicky 8 with added parallax sprite features for more dynamic visuals.
• Removed characters Mighty and Ray to streamline character selection and improve performance.

5. Final Release Adjustments

• Finalized Flicky release with additional bug fixes and enhancements to tubes.
• Announced the upcoming release of the GameMaker Studio (GMS) file for added user convenience.

These updates collectively bolster the Flicky Engine’s functionality, making it more reliable and enjoyable for all users. 

Developers and Contributors to the Flicky Engine

The Flicky Engine is a collaborative effort involving several talented individuals. Here’s a detailed rundown of the developers and key contributors:

Core Developers

• F4LK: The original creator who laid the foundation in 2017.
• A.NB: Took over as the primary programmer in 2018 and also contributed to level design.
• John-Kun: Responsible for porting the engine to Game Maker 8.x and additional programming between 2019 and 2020.

Code Assistance

• Noah Copeland: Offered substantial code assistance.
• Former Code Assistants: Contributions from TPOT, Great Lange, Mr. Potatobadger, AeroGP were also instrumental in the development process.

Level Design

• A.NB: Apart from programming, A.NB played a crucial role in level design.

Art and Sprites

• MrLevRocks: Provided the sprites making the visual aspects of the engine come to life.

Music

• MaxieDaMan (Michael Staple): Composed the music that complements the engine.

Beta Testers

A large group of beta testers contributed important feedback to refine the engine. Some notable testers include:

• Ashy, Illias, Polar-Star
• ScarlyNight, Capper, SoniKast, Starz0r
• Hexagonal, SoupTaels, Bluie, Dashboy
• Lazyhog (Welber13), GEONEO!!!, Noah Copeland
• Voltrix, DaveSkye, Speed TeX, TheValeev
• Dolphman, Lilac, MarioMan574
• CG (Calebe), CasaNova (and Flicky 8 Logo creator)
• MaxieDaMan (Michael Staple), mttwbarajas
• Savordez, Swift Fchar, Swag63

Their collective efforts have shaped the Flicky Engine into what it is today. 

Available Versions of the Flicky Engine

If you’re looking to download the Flicky Engine, here are the available versions you can choose from:

Flicky 8 Engine

• Version: 0.4.0
• Released: Approximately 4 years ago
• Price: Free

Flicky 8 Engine GMS (Game Maker Studio)

• Version: 0.2.1
• Released: Over 4 years ago
• Price: Free

Both of these versions provide the essential features and bug fixes from the original Flicky Engine, ensuring a smooth and reliable experience.