I have an issue

-wyi

So uhh I was trying to remake roborun.
https://studio.code.org/projects/gamelab/xW5204-FlaUVrqqMi5Ejvy5Sm86BSX8sKanUtw1deEM/edit
Something happened to the jumping function. Idk what, but none of the variables are working. Can someone help with this?

Varrience

Ok... so first off most of this code is unmaintainable, if you want to use timers, use an array not sprites, also don't set variables that your testing for inside an if statement they'll never execute like ever also airborn is not a global variable however airborne is which is why you probably can't move after you jump, though i don't understand why you need to booleans to test for if the player is on the ground or not, you could just use jumping indicating to the person reading it that the player has jumped and is airborne but you do you i guess
if (!jump) { WyiGlow.x = player.x; WyiGlow.y = player.y; } if (t3.x > 100) { if (keyDown("space")) { jump = true; t3.x = 0; fakewyi.y = player.y; fakewyi.setAnimation("playerflight"); WyiGlow.setAnimation("playerflightglow"); fakewyi.x = player.x+130; WyiGlow.x = fakewyi.x; t2.x = 25; player.setAnimation("invis"); t2.velocityX = 1; player.setVelocity(0, 0); } } if (jump) { if (t2.x == 30) { airborne=true; console.log("Airborne"); } if (t2.x == 60) { player.x = fakewyi.x+125; player.setAnimation("Player1"); WyiGlow.setAnimation("Player1glow"); t2.velocityX = 0; fakewyi.setAnimation("invis"); fakewyi.x = player.x; t2.x = 0; airborne = false; } }
anyways i think this is about the bulk that i changed of the project hopefully more issues don't come from the patch best of luck

-wyi

Varrience whats an array

Varrience

-wyi

timers = [] // or you can use the builtin constructor Array()

then by using the framerate calculations which is 30 (default) you can make timers based off second intervals.... or just use setTimeout which waits an amount of time before executing a callback

-wyi

Varrience ... oh jeez

ackvonhuelio

Varrience
the optimal solution is to have a loading screen to calculate all possible player inputs and reactions to those player inputs.
should only take a couple of minutes to load if you optimize it.
Of course, If you're willing to put in a bit of work, you could have a bunch of if(){} statements for each frame and decide what the reaction to the player input should be real-time(instead of pre-loading the reactions)
for example,
if(frameCount === 0){ if(keyDown("left")){ setTimeOut(function(){ if(keyDown("left")){ }else if(keyDown("right")){ }else if(keyDown("up")){ }else if(keyDown("down")){ } },1); }else if(keyDown("right")){ setTimeOut(function(){ if(keyDown("left")){ }else if(keyDown("right")){ }else if(keyDown("up")){ }else if(keyDown("down")){ } },1); }else if(keyDown("up")){ setTimeOut(function(){ if(keyDown("left")){ }else if(keyDown("right")){ }else if(keyDown("up")){ }else if(keyDown("down")){ } },1); }else if(keyDown("down")){ setTimeOut(function(){ if(keyDown("left")){ }else if(keyDown("right")){ }else if(keyDown("up")){ }else if(keyDown("down")){ } },1); } }

-wyi

-wyi wait a minute

Varrience

ackvonhuelio then why not use event triggers instead of putting it in a game loop? that way they would update in "real time" (btw real time hasn't existed for a while now mostly everything is adjusted for input lag but logically speaking it would update before the loop updates) and would start executing before the next loop began

ackvonhuelio

Varrience
ah, but that creates a dependency on a prediction of something happening instead of responding to things that you have mapped out and determined will happen beforehand. This can lead to the most common error in programming, which is something happening which you did not see beforehand.

Varrience

ackvonhuelio that's considered a logic error... and no i don't exactly agree with you, some code does actually require instant inputs for better scores or a prediction before the next hit is thrown this is especially apparent in demanding games with lower end hardware that can't put out the full framerate of a game, by doing this it mitigates it by a lot, and it much better than rubber banding the framerate if you ever see a game with that btw it's very nauseating

INTERNECION

Alright who used the flag wrong? C'mon man. I don't see anything here that deserves a flag. Next one's a warning

ackvonhuelio

it doesn't tell you who flagged?