WohlSoft Forums

Does this happen every time you start the level? If so, uploading the glitched level may help.

Here is a somewhat inefficient solution that may cause the frame rate to drop if your script is complex or too many NPCs are on the screen. (executed when the level starts, needs a variable to work) Do For v(a)=1 to sysval(NCount) With NPC(v(a)) If .x>sysval(Player1scrX)-100 And .x<sysval(Player1scr...

Changing the value of variables via scripts won't trigger these events. (changing them with events will do)
This is intended due to performance issues.

I did some experiments. itemslot= less than -20:Makes the player invisible -20:Coin Box -19:Cannon Box -18:Propeller Box -17:Spiny Mask -16:Goomba Mask -15:Buzzy Beetle Mask -14:Empty Mask (Placeholder?) -13:Rocket F.L.U.D.D. -12:Turbo F.L.U.D.D. -11:Hover F.L.U.D.D. -10:Makes the player invisible -...

As far as I know, even if the hidden code could detect if a key is pressed, I doubt whether there is another hidden variable standing for the key mappings of the players.

It seems that 38a forgot to implement this feature for auto-run events.

Let's make it even simpler. It's getting tricky now...
(executed when the player gets hurt)

Looks perfect, but I'm a bit worried about the framerate, as too many NPCs may result in laggy gameplay. FXCreate is an alternative choice, but effects is not as customable as NPCs.

DaveDaCat101 wrote:It doesn't work when I tried it... it just puts me at Mario.

This is what the script meant to do. It lacks something to be a complete SMB3 power-up system.

When players get hurt, there is an animation shown (switching between states), which causes Char(1).Status switching between two values quickly. Therefore, the following script trying to lock the player's state won't work. (executes when the player gets hurt) Char(1).Status=2 This one works because ...

I made it.
And the txt file:

DaveDaCat101 wrote:One question though, do you have to have the push blocks for it to work?

They are NPCs with scripts pushing players and generating bubbles, so they are essential.
You can replace their GFX with totally transparent ones so they won't show up in your level.

Use FXCreate to create effects. However, certain kinds of effects created by this way are glitched (for example, effect-113), as they are specially coded.
I made an example level for this.

This might be able to be done in vanilla SMBX 1.4.2 (which I was thinking about not too long ago actually, lol) with some scripting involved. I think this could be done, as there is a way to run a script when the player gets hit, but I'm still wondering whether there is a variable standing for the ...

When you click the "add" button in the "variables" window, two variables are actually created: a numeric variable and a string variable. The two variables share the same name. To use the numeric variable named "D", v(D) and val(D) are both OK. To represent the string va...