itch.io

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.

Yeah, just keep in mind that the more changes you make on the free version the harder it'll be to move to the paid version.

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).

That would be in "move_bouncing", though the issue is hard to recreate.

Discord is here https://discord.gg/kTX3pug. I'm not sure I would call this a Mugen alternative, but it's similar.

If you look at the code and the amount of features it doesn't compare to PFE, so that's why it's free ahaha. Also, auto turnaround is already in PFE, look at "auto_turnaround_passive" 🙂

Well, I finally got around to it.

Please read through the tutorials on the website, they cover all of the basics for modifying the engine https://platformfighterengine.github.io/#/tutorials

You can modify any part of the game and do (almost) anything that GameMaker supports.

You can use whatever assets you can import into GameMaker. Try it on the free version.

That isn't supported by default, but you could give the character a custom "draw_script" that checks which way they are facing and draws a different sprite instead.

Right now there's no support for having 2 players on 1 keyboard - the issue is that it allows you to rebind the entire keyboard, so there isn't a defined "split" in the keyboard. But that's a good idea for a new feature.

Yeah, that's pretty much it.

You can join the PFE discord and then send a DM to Yosi if you want to talk about PFE stuff in a private space.

I don't have experience with console porting. Most of the gameplay logic should transfer easily, but there could definitely be issues with the graphics and networking.

1. 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.
2. 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.

First full release is already available on the page, it's the "[Older Version] Platform Fighter Engine 1.0.0.yyz" file.

I don't have the time to work on something like that right now, but I'll think about it.

Which version number do you want specifically? The first beta version or the first full release version?

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.

In "game_settings", change the macro "player_hud_type" to "HUD_TYPE.legacy"

I've removed older intermediate versions from the page to reduce clutter. If you need to download an older version for whatever reason, send a message and I'll add it back to the page 👍

This is the minimum code required to add an option to the menu. You'll still need to add code that checks the setting, as well as modifying "match_settings_save", "match_settings_load", and "match_settings_default" so replays work as intended.

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.

What part in particular are you stuck on?

Add these lines after Line 5 of obj_fspec_shadow_flare_ball: User Event 0

if (!instance_exists(_target) || _target == noone)
    {
    instance_destroy();
    exit;
    }

Depending on the version you're using, you may not have (or need to set) that macro.

Take a look at how the existing EX specials work. For example, the script "fspec_afterburner_kick".

The projectile itself needs to either have an overlay sprite and use the default draw event, or have a custom draw event.
Also - do you have a Discord account? The Platform Fighter Engine Discord server is a lot more active than the itch.io forums.

You would need to change the "css_ui_create_player" script.

The area the cursor is restricted to is set in obj_css_ui: Step: Line 142

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;
    }

You only need to purchase it once, and then you can share it with other people in your company.

Ah, if the sprites are VERY large, it could be a texture page related issue (the game has to downsize them to fit them on the page). Either way, glad you found a solution!

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);
callback_add(callback_hud, limit_gauge_hud, CALLBACK_TYPE.permanent);

I'm not sure exactly what you did, I tried adding a grid sprite to a stage and it shows up pixel-perfect

When you're adding the sprite to the room, are you leaving it at 1x scale, or scaling it down?

Do you have camera zoom enabled? If the camera zooms out, sprites will look more pixelated.
On the default settings (without camera zoom), sprites should look exactly the same in the editor as they do in-game.

For saving and loading, you could add a "coins" value and "locked_characters" value to the "stats_load" scripts, which will allow you to use the "stats_*" functions. You can also just use default methods for saving and loading data (look up GMS2 tutorials).
In order to handle locking/unlocking characters, you'd probably want "obj_css_zone" to check the "locked_characters" value to see if its character is locked or not.