Super Mario Bros. X Forums

https://ibb.co/Mfr1vSX
https://ibb.co/Jdvvv9N

Code:
```
local timer = 1280


function onStart()
startlayer = Layer.get("Toxic")
end


-- Run code every frame (~1/65 second)
-- (code will be executed before game logic will be processed)

function onTick()
if timer <=0 then
triggerEvent("comeback");
timer = 1280
end
if timer == 496 then
triggerEvent("warn")
end
if timer == 378 then
triggerEvent("warn")
end
if timer == 256 then
triggerEvent("warn")
end
if timer == 128 then
triggerEvent("warn")
end


if startlayer.isHidden then
timer = timer-1
end
end

-- Run code when internal event of the SMBX Engine has been triggered
-- eventName - name of triggered event

function onEvent(eventName)

if eventName == "goaway" then
timer = 1280
end

end

function onDraw()
Text.print(timer, 100, 100)
end```

Events:
goaway
comeback
Toxic
warn

1. Important - In my attempts, I have only found one block that works well with this. That's block 673 the "Instant Kill Block". Simply replace the graphic with your own (preferably 75% opacity) eerie neon color. I tried other kill blocks like lava but these have a weird glow effect that does strange things.
2. Make sure all the blocks you place are on a dedicated layer (here, it's layer "Toxic"). Set up a switch block to toggle the event called "goaway".
3) Here's why you need Lua code. You'll need to create a timer to specify when the Toxic layer reappears. Technically, you can do this through the editor using an event, but keep in mind that if/when a player hits the next "goaway" switch, the previous instance of that event will still be counting down. Also, if you have a timer/warning sound, it would be tied to that event and continue to go off even if you've hit the next switch. Use code to create a timer variable, and to trigger the "comeback" event at 0.
4) Another stumbling block: Be sure that in your code to trigger the event "comeback" you also tell it to reset the timer to 1260. Reason is if you don't, the code will loop, since you're timer is stuck at 0 it'll spam activate the "comeback" event and bog down the game significantly. This is going to be crucial because if you maintain any areas in the level where the Toxic layer is not present (tunnels, safe areas etc) once that timer goes down to 0 the code will basically become an infinite loop of doom.
5) Be judicious in placement of the "toxic" blocks. If you can't reach a distant area before dying, don't place blocks in it. You have a limit of 16k blocks per section, which doesn't go as far as you'd think. You'll probably need to plan this kind of level in multiple smaller sections.
6) The temptation will be to make the timer correspond to seconds & simply alter the countdown factor in the code. I used 1260 which is 64 frames x 20 seconds. Unless better minds than mine know of a way, be advised that using a factor such as .01 will turn your timer into a decimal and wreak havoc with your encoded warning timers. I tried various workarounds but ended up deciding that seeing 1260 count down over 20 seconds was better than not being able to have a "warn" sound for the player.