Oh, also, HorvatM actually mentioned WaitForVIP (twice, but not really what it does. That was exactly the solution you needed, though.
The six VB demo games also use vbWaitFrame(0), which does pretty much the same thing. I’m kind of surprised you didn’t find this earlier – maybe because it’s the VB with its limited processing power. On a PC you would have found out pretty much immediately that your game runs at a limitless FPS, which can’t just be solved by saying “slow it down with this counter please”. Especially since PC processors are all different speeds. 🙂
Edit: sorry all the tabs turned into double spaces, by the way. Hope you can live with that. 😡
I see, that’s interesting, because there’s no need at all for those functions to be ints. They don’t return an integer value…. They don’t return any value at all (which is why I changed the functions to type void in the first place).
…I just tried declaring the voids before int main, and it’s not complaining at all?
void initgame(); void preintro(); void intropart(); void titlescreenpart(); void charselect(); void prefight(); void fightscreen();
Don’t forget to use the right type, I guess? If your functions are all voids, it’d be weird to declare them as ints at the beginning of your code…
The way you have set it up, it sounds like the pattern would be very predictable: press L or R, and you will most guaranteed see the enemy jump, then punch, then try a special.
Here’s my tip: randomize it, and randomize it based on a timer (that counts up by 1 each frame) and your character’s proximity to the opponent. Actually, have two randomized timers: one determining the enemy’s movement, and the other their actions.
For the movement timer:
Once it reaches its max value, it is time to perform a movement action. Then do a check how close/far the opponent is from the player.
– If they’re further than, say, 200 pixels away, then always move the enemy closer by, say, 100 pixels.
– If they’re between 100 and 200 pixels, randomly decide if they should be moving a random amount forward, do nothing, or move backward a tiny bit (you can influence the chance this happens by comparing their HP, too).
– If they’re closer than that, randomly decide whether they should move forward a random amount, do nothing, move backward a (larger) random amount, or jump.
For the action timer:
This timer needs to be a little bit shorter (so moves are attempted more often), but still at random intervals. When it’s time to decide on an action:
– Check whether the player is in, say, a 50 px proximity. If they are, attempt one of the moves (or do nothing). This way, might try to attack even when it’s not close enough this way, but it’ll just look as if the enemy attempted and failed at an attack, which gives you, the player, a chance to retaliate.
Outside of both:
– If the enemy is jumping and near you, it could randomly try to do its special move right afterward.
You can add to this, and add more conditions that specifically change the behavior based on which bug it is, how aggressive/cowardly they are, if they’re almost out of HP, etc.
The issue
Now, there is one big problem. All of the logic above relies on randomization. That is, the kind of logic that looks like this:
int random_number = (select a random number between 0 and 10);
if (random_number < 5) {
//Perform action of type 1
}
else {
//Perform action of type 2
}
The big problem is that the VB doesn't seem to have a function to create such a random number! There's no rand() function (like in traditional C) to rely on to give you a random number. That's going to complicate things. I've found a potential random number generator you could use but I need to test it first. In the meantime, think about the fighting logic like the above a bit more, try to expand on it, and carefully consider how you would start implementing it. 😉
Edit: and now we have a solution. 🙂
http://www.planetvb.com/modules/newbb/viewtopic.php?topic_id=3723&post_id=30500#forumpost30500
