@Moh_Animator Yeah, but even in beta you have to playtest and look for bugs.
Agreed, but I don’t think he had time to notice bugs in the HTML, at least now he will know.
I don’t think he had a deadline for this, but I still think that if he didn’t have time is not an excuse.
the JS Math object is broken in the beta. It wasn’t working in the editor, so I have absolutely NO idea what’s happening.
This just happened to me too. I think since the player is panning the camera to him WHILE the vcam is rendering at the player’s coordinates, causing this to happen.
I think the game saving thing causes that. It downloads a file containing all your data.
Every time you hover the mouse on the buttons, it slows down the game A LOT.
I think Math being broken causes this. It’s been a problem playtesting on my own computer because it takes up so much RAM.
The Math object might be broken due to the way wick does scripts. It uses the dreaded with
statement, which requires you to add the required variables in the object the code is being run with.
I use Math.round to calculate what percentage of the level’s collectables have been, well, collected. This only breaks 1-1 for some reason.
Maybe there being a string in a mathematical expression does something?
Math
doesn’t support strings.
Try wrapping it in a toString
.
I think an alternative would be to use it in the blahblahwhatever.setText()
instead that’s a few lines down from here, since it’s easier to instead use
Purrcent.setText(project.completePurrcent + "%\nCollected!")
Oh! This was a classic error:
// code
var x
=
Math.round(.25)
// what programmer sees
var x = Math.round(.25)
// what js sees:
var x = null;
=; // ERROR
Math.round(.25)