Recent content by CloneFighter

I can't seem to be able to check the cards' descriptions in the shop when they're part of a Suite. They all just say "Unavailable" when I try... The individual cards' descriptions appear just fine, though, so I think it's an issue exclusive to the Suite menus.

Small thing worth mentioning: with how much space the UI takes up, it might become a bit hard to see ahead of you in resolutions with a more square aspect ratio (such as the game's default 8:5). Consider either reorganizing it or slightly shrinking it down (closer to the size it is in BAZR, maybe?)

How exactly are you making the loop-de-loop work?

I know I'm late to the jump, (congrats on getting it working!) but basically, it should look a little like this mockup I threw together right now: The green line here is the line defining the slope.

This is why it's advised to align the control sector of a sloped FOF with the in-map sector containing the FOF. The slope is pinned to the linedef defining it -- the platform technically is tilting properly, just relative to the control sector instead of the actual map space. Make sure the...

Slopes cannot move on their own. You need to add the Dynamic flag to the slope's control linedef to let the game know that the slope can move. It's right here: Do note that the way you have this set up, only one side of the slope will actually crumble. I'm not too sure how to fix that...

Then your best bet is to mess around with the functions the game gives you, yeah. Start small! A good first-time practice is to just think of a simple ability - say, a double jump that halts your horizontal momentum - and try to write it into the game. Then you can build up to making whatever...

I'm not sure if this is supposed to take you out of bounds. But it does. And it's hilarious.

You can't really do it based on height, but you can easily check for their downward momentum. In pseudo-code, it would sound a bit like this: Hook PlayerThink, with player: Check if player meets the conditions to be affected by our changes (playing as the right character, etc.) If not defined...

I'm already sorry that you have to bare witness to the code horrors that lay beneath the original textbox library, to be honest... That aside, this looks interesting so far! Looking forward to playing this and getting stuck at a spin gap /silly 1747611970 Also, just sayin': Fang really DOES fit...

Neither of these are a solution. There's an entirely separate effect for this type of thing - linedef type 544, aptly named "Current".

Like I said in the previous thread about this, you can change the value that's being added to p.lastShotTime to change how long the cooldown lasts. If you want it to be around Cuphead levels, I suggest TICRATE/5, such that it fires 5 shots per second.

You're setting p.lastShotTime to leveltime. That means that on the very next tic, leveltime - p.lastShotTime evaluates to 1 (since leveltime increased by 1), which passes the check (1 >= 1) and sets p.shotCooldown back to 0. Essentially, the code you wrote DOES add a cooldown... of exactly one...

Yeesh, the lack of formatting makes it really hard to read. Allow me to put this whole thing in a code block and add the proper indentation... local invulframes = true local ghost = true local c1 = BT_CUSTOM1 local skin = "vestige" local cooldown = 6 local starttimer = 290 local candash = false...

Allow me to reformat what the AI wrote for you to make it a bit cleaner to read... addHook("PlayerThink", function(p) if p.mo.skin ~= "sonic" if (p.pflags & PF_JUMPED) and (p.cmd.buttons & BT_JUMP) then S_StartSound(p.mo, sfx_s3k75) local boost = 5 *...