Can you post an example image of other colors getting confused for white, with the palette & sprites used?
Springroll Games
Creator of
Recent community posts
Make sure you're following the correct palette format. The first column is the sprite colors, while the other columns are the in-game colors. https://platformfighterengine.github.io/#/tutorialB6
I'm not a Github expert so I'm not entirely sure. I know that you can make a new repo, download the old version of PFE you based on the project on, commit, then download the new version of PFE, and that will show you all of the changes. But I don't know if there's a way to go from that to adding all the changes to the project. Maybe if you use a separate branch for it and then merge the branch back into main.
It was only a few attacks, you can do a Ctrl + Shift + F for "is_reeling" and see which attacks incorrectly used that variable name.
As for updating projects, unfortunately there's no universal way to do that, it depends on which scripts you have changed in your project. You definitely want to use some kind of source control program like Github Desktop. If you haven't made too many changes yet, it would be easiest to make a local package of all your changes and then import them into the new version of PFE, but if you already made a lot of changes, it would be easiest to take the updated files from the new version of PFE and move them back to your project.
The free trial version is missing online features, as well as some offline features that use the same functions, such as being able to rewind replays.
There are no time or size limits; it's just a downloadable GameMaker project file.
Transferring a project from the free version to the paid version is difficult (you'd need to merge the two projects with a source control program, which is very time-consuming).
Discord is here https://discord.gg/kTX3pug. I'm not sure I would call this a Mugen alternative, but it's similar.
Please read through the tutorials on the website, they cover all of the basics for modifying the engine https://platformfighterengine.github.io/#/tutorials
- Generally ports should work, but GameMaker is known to have obscure platform-specific bugs. There are also some functions (mainly the ones dealing with the file system) that only work on Windows or Mac.
- You should be able to test online with 2 windows on the same machine if you do it in this order:
1. Open the game exe. Set the "Target Port" to a different number. I usually use 63567. 2. Open another game exe. Set the "Ingoing Port" to the same number. 3. On the first game, do "Join with IP" and type in your local IP address. 4. Accept the join request on the second game.
If you look in the character init scripts, the "sprite_scale" variable is set to 2 by default. This is because all the characters in base PFE are scaled up 2x. If you change it to 1, then the sprites won't be upscaled and you'll have more pixels to work with. Also, make sure the camera is zoomed out enough.
You'll want to
1. Add a new variable to the _settings struct in game_settings for the new option.
2. Add the name of the new option to match_settings_choices in obj_css_ui: Room Start.
3. Change the Step and Draw End events of obj_css_ui to handle the new option.
Once you've added all the rules to the menu, you can decide where to put the code that checks the match settings and applies the rule. That'll probably be in game_object_setup.
Put this code at the start of custom_limit_gauge:
//Variables if (!variable_struct_exists(custom_script_struct, "limit_gauge")) { custom_script_struct.limit_gauge = 0; }
And this code at line 8 of hud_limit_gauge:
//Variables if (!variable_struct_exists(_player.custom_script_struct, "limit_gauge")) { _player.custom_script_struct.limit_gauge = 0; }
1. Add this code to the "custom scripts" section of the character init script you want to give a limit gauge:
callback_add(callback_passive, limit_gauge_passive, CALLBACK_TYPE.permanent);2. Change the player_hud_type macro to HUD_TYPE.legacy (so you can see the gauge on the HUD)
callback_add(callback_hud, limit_gauge_hud, CALLBACK_TYPE.permanent);
3. Change the character_static_attacks macro to false
4. Make sure the script "limit_gauge_passive" is spelled correctly (looks like I a made a typo in 1.3.2 that wasn't in 1.3.1, so double check that)