Each ship will have 6 values:
-Pos_x
-Pos_y
-vel_x
-vel_y
-health
-movement_progress

Each will be an int.

There is a max of 150 bullets onscreen at any time, where bulletarray[i]=x and bulletarray[i+1]=y

For the ships, when movement progress is 0, it follows the general
movement of the rest of the ships as specified by int Direction. When movement_progress is not 0, the ship is following a path downwards towards you, and helps keep track of when to make turns and such.


Things I need to figure out:
How enemies will know where to go to when they get done with their decent downwards.
How enemies will be stored.


int x and int y are the X and Y positions of your ship respectivly
scrbuf is the screenbuffer I am using.



More to come

Will you be keeping track of which bullet belongs to which ship (I don't think it's necessary). For the bullets, you might also need to keep track of vel_x and vel_y (if bullets have nonstandardized velocity) or just direction (personally, I think vel_x and vel_y is easier, so you can just do x+=vel_x and y+=vel_y on each physics tick). What about keeping track of the damage dealt by each bullet in the bullet array, in case you have multiple types of bullets, which I presume you might?

I think I might just do two arrays, bulletarray and enemybulletarray. As for the velocity of the bullets, they shoot straight forwards, so I just subtract two from the Y of each bullet every time Right now, I don't have multiple types of bullets, so I'm not sure. But it does sound like a good idea

Edit: It just occured to me that if I have a type for the bullets, be it damage or something, that I could have a type(s) for the enemy too

Aww, they all shoot straight forward? So no weapon upgrades that will let you spray a curtain of bullets in every direction?

Oooh, that is a good idea I'll work it into my code

Edit: Is this what my struct array will look like?

struct mystruct {int,int,int,int,int};
mystruct array[2]={0,0};

Not a very helpful one!


Code:


It's not the funnest thing ever to initialize an array of structs with the {} construct, so try something like this:


Code:

Earlier KermM said something about malloc not being able to be global, any way around it?

Let me be more specific. You can't malloc() things in the global scope itself. However, if you declare a variable like struct myType* myVariable = 0; outside of any function, then malloc() it near the beginning of your main(), you can easily use that in other functions. Just be aware that it's a pointer, of course, and to be safe, make sure you check that it's not null anymore.

Not sure I fully understand, could you post a specific example please? Like a code example.

Sure thing, here's something completely arbitrary:


Code:
I'll have to double-check that initialization statement (ie, struct myStructType* myArray[] = null;).

Code:


Is that about right?

Ah, I see you're not familiar with pointers, which is going to make this a little more difficult to explain. Other than your note about the *asterisk (not "asterik"), it's all correct.


Code:
The *myArray means that myArray is actually an integer holding a pointer to the contents of my array. The * looks inside myArray and gets that address. Then, the [1] essentially moves (sizeof(myStructType)) bytes forward in memory, then the .x moves a little bit more (in this case 0 bytes). We'll have to give you a formal introduction to pointers at some point, and how the * and & operators are used.

Ah, ok. Yes, pointers always were confusing to me x.x

Is there anyway to have functions within the Main() function?

What do you mean, like sub-functions? No. What would be the point of that? Perhaps if you can explain what you'd want that for I can explain the proper way to do it.

This whole thing with pointers seems like too much work

Fine, then there's a different way to do it, but it's basically the same thing. And don't wimp out about pointers just because they're scary! Press onward! Face challenges! I didn't start out knowing all the languages I did; I had to stare at other people's code and be confused first!


Code:

KermM helped me tonight with getting my code to work, apparently it was segfaulting. He gave me a fix, but when I tried that fix, and then another equally good fix (in terms of the segfault). I'm going to work on this tomorrow when I get time. One thing I think might be happening is maybe AB (an int* pointing to bulletarray) is becoming 0, or the wrong value.

Oh, and I learned about short circuiting. 0 && 1 will check 0 first, which is not true, and stops testing values. 1 && 0 will check 1 first, true, and then check 0. [note: this was for self reference ]

_Player, we can certainly continue looking at your code today and try to track down what's happening to ab. It's a shame that there's no stderr or stdout to help debug program. Oh, and don't forget that short-circuiting works with both the logical or (||) and logical and (&&) operators.

Can I get some help with this? Here is the relevent code:

Code:


Right now, when it tries to run, it doesn't even start :/ At first I thought it was the short circuiting thing, that didn't work. Then I tried changing the "while (i<1200..." part to "while (i<1100..." that way there was no way to cause a segfault. But it still doesn't work :/ Thanks in advance

Just to check, my previous fix did the trick for a while, right? Or is this still the same thing with no luck?