runouw.com

EDIT: Redacted for Runouw's sake.

...what exactly is different?

Play my level "Orb Evasion." Play it on both RC2 and RC3. Go on either Level 2 or Level 3. It's the perfect example.

EDIT: For those who don't feel like testing that out for yourselves, this is the issue:

My gravity contraption in Level 2 is supposed to use a perfectly precise Relative value - which is on repeat - with the Move Character function to make the player float upward slowly just enough to not float downward constantly, yet not rise too quickly, all while the gravity direction is at 180 degrees. In Release Candidate 3, because the Move Character function is weaker, the player will rise rather quickly, and this makes it impossible to go through the obstacles because you have to remain at the same altitude for longer periods of time to progress.

In Level 3 I introduced a trampoline that varies your bounce height depending on when you jump from it. Jumping just as you land on it results in a really high bounce, which is needed to reach the alternate path. In Release Candidate 3, because the Move Character function is weaker, the player won't bounce as high, which makes it impossible to reach the alternate path.

they're release candidates

i'm pretty sure release candidates aren't final and assuming they are is a mistake

All that happened was I discovered this issue at one of the worst possible times: during a moment of depression.

When I'm depressed, I shouldn't be making any contact with anybody, because I'll just sabotage myself to make more problems as if I deserve them.



Runouw has a whole lot to work on; crushing bugs takes a bunch of effort and care; nothing has ever been finalized. Can we please move on?

Snapshots/RCs are always prone to have features altered and changed. Nothing is set in stone.

Personally, I think you could label what RC fits your level's physics, and the player can then go find that. But yeah, not much else to do but expect change, and then apply the new math where necessary.

Totally understanding as to why you're snappy. Been there, still there, they haven't refunded my ticket.

(If you want, I can try To find what was changed and where, and give you the formula)

Lahat na Weapon.

1. Left Weapon: Masamune
2. Right Weapon: Amethyst Staff
3. Accessory 1: Full Iron Armor
4. Accessory 2: Gold Ring
5. Accessory 3: Cursed Amulet
6. Boots: Winged Boots

Kimonio wrote:(If you want, I can try To find what was changed and where, and give you the formula)

I figured out the formula on my first try. It is so friggin' simple:

In RC3, simply double the Relative/Absolute value in any given Move Character function and it will then work EXACTLY how it did in RC2.

In other words, the Move Character function in Release Candidate 3 is half as effective as it was in Release Candidate 2. Mission accomplished. And I complained for nothing.

It turns out the because a bug in the relative speed triggers was fixed, I accidentally broke any level using version .5 that was using those triggers. You can fix it by doubling the "yspeed" value. Or you can code edit your level back to .4 (by also removing the equipment) and then loading it again. This will automatically multiply every single relative speed trigger by 2 (because I originally intended to have this upgrade work seamlessly, but I accidentally neglected that upgrade the .5 version levels).

And Runouw takes another win, lol.


Also, I found a new bug. If you press backspace while warping through an Exit Portal/Wormhole, depending on how long you waited, there may be a few side-effects: the HUD display is gone until the game window is closed out, and the player is slowly attracted towards it while being unable to re-enter it, making the level impossible to finish.

I don't think this existed in RC2. Or am I mistaken?


EDIT: Never mind about the HUD display disappearing. I must have pressed another key while trying to respawn from a wormhole. The "\" key toggles the HUD display, apparently.