Search results for query: *

Decided to look through these because why not? Pretty nice set of maps, if small as it is right now. Got a 28 second time on Ireland. Absolutely beautiful stage. /silly

That would need a separate mod...

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.

...it. If player has landed (here's one way to check that), and player.prevmomZ (IMPORTANT: account for flipped gravity here!) is less than, say, -16*FRACUNIT... ...then spawn dust particles around the player (multiple ways here, but I'd use this one). Update player.prevmomZ for the next tic...

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...

...player.charflags = $1|SF_RUNONWATER player.normalspeed = skins[skin].normalspeed+10 player.jumpfactor = skins[skin].jumpfactor*2 player.acceleration = skins[skin].acceleration+5 player.camerascale = skins[skin].camerascale*2 player.mo.blendmode =...

...if (p.pflags & PF_JUMPED) and (p.cmd.buttons & BT_JUMP) then S_StartSound(p.mo, sfx_s3k75) local boost = 5 * FRACUNIT local upwardBoost = 6 * FRACUNIT local angle = p.mo.angle p.mo.momx = p.mo.momx + FixedMul(boost...

The cooldown entirely depends on the length of the S_PLAY_FIRE and S_PLAY_FIRE_FINISH states, from what I can see. As long as the player is in either of those states, they cannot move. Assuming player is the player struct of the player in question, their current state duration is stored in...

You misspelt ability as abiliy. Don't worry, even the big wigs make the slightest mistakes sometimes ^.^"

Sounds like ZB is trying to check for some things that are already gone. A lot of these errors are regarding Pipe Towers Zone's textures, which were dramatically overhauled in v2.2.14 and then reverted in v2.2.15. In other words: correct me if I'm wrong, but I think this is pretty much normal...