OK this is just advice so don't take it the wrong way. I looked at the code and I found it hard to follow. I think it will become unmanageable as your game gets more complex. Without adding any more language features just now (structs and whatever will help in the future..), try to identify all the 'things' in the program and what variables each one needs. Then group these together and name them consistently.
Then look at everything that needs to happen and group those into sections in the main loop with comments to explain what is happening.
Then, I think, you will find it easier to see the patterns and where the code does not match your intention.
For example, I'd say you have two players and two (later three) fireballs - so put the variables for each one of those together. And, in terms of actions, you've got things like 'Process input', 'check if on screen', 'move player', 'move fireballs' and so on.
In practical terms I noticed that when destroyBG gets set to true it never gets set back to false and the code reloads the 'bg2.png' bitmap every cycle which looks wrong to me.
Also, you can start a new topic every time you have a new question, or continue on the old one but don't do both!
[edit] Line 367-389, this doesn't look right;
#SelectExpand
1 if (fireballUpLV2
)
2 {
3 al_draw_circle(cX3, cY3,
20,
al_map_rgb(200,
200,
50),
5);
4 cY3
-= speed
+ 5;
5
6 }
7 else if (fireballDownLV2
)
8 {
9 al_draw_circle(cX3, cY3,
20,
al_map_rgb(200,
200,
50),
5);
10 cY3
+= speed
+ 5;
11
12 }
13 else if (fireballLeftLV2
)
14 {
15 al_draw_circle(cX3, cY3,
20,
al_map_rgb(200,
200,
50),
5);
16 cX3
-= speed
+ 5;
17
18 }
19 else if (fireballRight2
)
20 {
21 al_draw_circle(cX3, cY3,
20,
al_map_rgb(200,
200,
50),
5);
22 cX3
+= speed
+ 5;
23 }
fireballRight2 should be fireballRightLV2 ? This is what I mean about 'patterns'
]]>
