WohlSoft Forums

Nice. The physics look like they're pretty close to SMBX now. And I like the text box for typing in cheat codes.

The image was working just fine until I got the latest version of the editor. Then the mask quit working. I don't think the images are the problem, but here they are: background-1.gif background-1m.gif This is probably just another one of those weird errors that only occur on my computer. That has h...

The name is fine, and I just updated the config pack. The problem did not go away.

Timers are counting down when the player is growing or shrinking. This causes problems with event scheduling, particularly with moving layers, because all layer movement stops while this is happening, and then the layers change speeds at the wrong time. There needs to be something like what happens ...

The editor is unable to load a custom mask for BGO-1. It just uses the default mask.

I have a couple of minor suggestions: 1)Make it so you can place more than one of any item in a box, and decide if they come out one at a time or all at once when you hit the block. There could be an "infinite number" option as well, and a "randomizer" option. This option would a...

I just experienced a similar problem. I used layer:stop() and the layer seemed to drift to the right a tiny bit. This is odd, since the layer was only moving up and down.

If I send a signal before a coroutine is waiting for it, it throws an error. I think there should be a built-in safety for this function. It could simply be this condition: **NOT ACTUAL CODE** If a coroutine is awaiting this signal then send the signal end (I see somebody made it so TAB can be used ...

The timing with the waitSeconds function isn't consistent. I moved multiple layers, at the same speed, for the same amount of time, and they weren't aligned afterward. Also, I tried waitSeconds(1) and waitFrames(65) at the same time, and they weren't aligned afterward. These wait times should be equ...

What about NPC-104? There's only a Y-speed AI field for that one. Ok, just got it to work (with SMW plaforms only. still can't figure SMB3 platform). However, gravity still tries to move the platform, and it starts moving down a bit before the script runs on each loop. This makes it drift downward s...

I can't set the platform NPC's speed. Regardless of the value I try to set, its behavior stays as normal. Actually, setting the speed fields doesn't seem to do anything to any NPC. So, how can I override an NPC's physics so I can directly control its movement?

Is there a way to change a BGO's grid size in just one level or episode, without changing the global bgo.ini file?

This is supposed to wrap all platform NPCs and create a sensor in the center of each one. It doesn't do that. And the first time I tested it, it made all the platforms act like they were set to "friendly." This only happened once. function onTickEnd() for ind,npc in pairs(NPC.get({60,62,64...

Hmm. I must have been partially blind that day or something.

Yeah, there is NOW. When I posted this topic, that wasn't there. There was just a vague-sounding "type" field there that I couldn't figure out how to use.

I need to make a script that grabs all platform NPCs and wraps (with pnpc.lua) any new ones that spawned in the current frame , then creates a collider in the middle of each platform NPC that has just been wrapped. This collider must be associated with that NPC (That is, the same collider must be pa...

Each BG image rendered with this API seems to be shown in every section, regardless of what was set for the "sections" property.

I've noticed that music and SFX played with the SDL mixer functions are still played if the "Disable Sound" box is checked in the SMBX launcher.

I have a script in onTickEnd that attaches some hitboxes to the player with colliders.lua. The hitboxes still seem to be positioned in the player's position before the physics calculations are made. Since I switched from onLoop I don't see any difference between the two. The hitbox positions lag beh...

Adding the player's speed is not the correct solution here. That's only accurate in some cases. First you want to make sure you have LunaLua 0.7.3 installed. Then, instead of using onLoop, which is now deprecated, use onTickEnd, which will run after physics calculations and put the colliders in the...