No, .setboy only sets the level at witch the robot floats at. It has nothing to do with the mass since mass effects only to z-axis gravity (not y-axis gravity) but I still want mass to be calculated into the formula.
Should nrg be charged constantly or just when bots change their buoyancy. I think the latter.
Think of a hot air balloon, you constantly have to keep the air worm or the balloon will sink.
The thing is I don't want buoyancy to end up working just like a '90degree .setaim and N .up' commands , but I do want to charge it with voluntary movement costs.
Robots will start at zero (button of screen), a max value of absolute 2000 means float to the top of the screen.
Hmm, I am still considering it though. Can you give me a formula you had in mind? I'll think of something myself.
I am thinking we will take voluntary movement cost, multiply that by mass, multiply that by Y-gravity, multiply that by a value. But what should the value be if a robot can remain buoyant indefensibly?
I don't want robots to slowly lose buoyancy because this yet again makes it look like the '90degree .setaim and N .up' commands.
I am going to use Y gravity itself to float the robot, I have not tested this yet but the idea is:
Let's say the robot is set to half way up the screen.
If the robot is above that point the Y gravity is down.
If the robot is below that point the Y gravity is up. (reversed)
The idea is, the robot should start bouncing at half way up the screen, and if there is enough friction (this one will be fun to test) the robot should stabilize at half way up the screen.