PGE Forums

That's obvious. However, 38A often misses these details, for example how he could not notice the dim "fix" broke "with" blocks? That would have been fairly easy to notice. If he wasn't able to replicate this bug and it works as expected, he should either reply me telling how to f...

Not fixed or replied to yet.

When you use a dim variable and then use a "with" block, accessing to this object's variables will result in "Access Violation" error. For example: dim i as integer with npc(1) .xsp = 1 'stops the script end with This bug breaks basically all my scripts. By the way, it reminds me...

Not to mention the incredibly amount of work is it to include an online mode. If you really want to play online use Parsec.

1) In the debugger window, the npc counter occurs that when an immortal npc is killed with its property alive=0 it is not discounted, but this does update when a normal npc dies, weird isn't it? It happens with all NPCs overall. It seems .alive doesn't completely kills NPCs, so you've got to use nk...

I just tested it and it's pretty cool and well done. Good job!
Don't forget upload screenshots when you can

When the player gets hurt, he won't be able to stomp/spin jump NPCs for a little too long:

Spoiler

Honeycam 2020-08-27 20-07-22.gif (262.93 KiB) Viewed 53 times

If there's a timer to prevents the player for doing that, please set it correctly according the time the player cannot move in the hurting animation (38 frames)

When getting a "special" power-up (Leaf, Tanooki Suit, Hammer Suit and/or Frog Suit). I call them "Special" because they have a different animation

Currently, the .stand property for players is read only. Can you please make it writable too? I'm making custom physics that relies on the movement of an NPC, and there are a few animation errors I can't fix due "stand" being incorrectly set (for example, sometimes the player is on landing...

This function returns true when player cannot move after getting a power-up/getting hurt (37 frames for powering up/down, 11 for getting an special power up) Read only. It's really hard (or even impossible) to detect accurately when the player is frozen due powering up/down without using Autorun eve...

Wow it looks really promising! Can't wait for play it.

In fact, players shouldn't be able to slide Seesaws at all . I reported in multiple times, in SMM2 you can't slide Seesaws because if you do, you couldn't jump crouched and the jumps would be significantly harder. (In SMBX you can crouch midair but there are still situations where you slide accident...

Variables initialized inside "if" statements doesn't seem to work correctly. Their operations drop random values (probably due a wrong memory address reference?) For example: if -1 then dim i as integer = 1 dim j as integer = i+2 dim k as integer = j-i call showmsg("i:"&i&...

When I force the player to face to a specific direction while is holding an item, when I press the opposite direction of which is facing the carried item shows in the wrong position:

When NPCs collide into a wall they face the opposite direction. While this is great, it's a bit annoying sometimes, especially since there's no an easy way to disable it. Can we have a function to prevent NPCs facing the opposite direction when colliding into a wall? And when a wall if sound, the .x...

Ah, I see. This post explains it pretty well: https://www.supermariobrosx.org/forums/viewtopic.php?f=101&t=23744

Scripts made in 1.4.X aren't compatible with SMBX2 and vice versa. They're two completely different programming languages.

I wrote this code: struct npc_struct dim ivala as integer dim ivalb as integer dim ivalc as integer end dim mynpc as npc_struct mynpc.ivala = 1 But when struct variable is called, it gives me a "Runtime Error (Access Violation)" in the debugger: error.PNG And the script stops executing. Is...

Just what I thought. The maximum texture size the game can render depends on your hardware, yours support 2048*2048 so that's why you can't see the animated backgrounds while others can. The only reasonable fix I see 38A could apply is increasing the minimum limit to 4096*4096, but I'm not sure what...

This sysval would determine the lasting time after the player died and is send back to the world map (or if enabled, repeat the level). This would be super useful for doing our very own death events/effects! This would apply only when the player-1 died and there's not a player-2 (either is dead or n...