I read you shouldn't use c_move more then needed. I've examined the usage many movement/gravity codes with moving and gravity combined(even in manual they are in same function). The thing is i would like to create an independant function for calling gravity for all entities that are active (player and enemies alike).
Would it be more feasible to create a single gravity for the player and one for all enemies: both variable. (main idea is gravity values might change for certain area's, thus why i think an external function might be better... since it can be called when needed and/or using changed values).
Tho i believe having too many instances of the same function going, might be a performance issue.
Or should i just use 2 c_move's one for player and one for enemies(containing both regular and gravity movement).
can anyone please help. i just dont want to have 5000(exaggerated) c_move calls going at once.
Perhaps a small external function example(if that is how it should its called).
I've read the newest manual a few times also few diff lite-c tuts, So please pardon my noobness but i feel like i already know this, its just been along time.
GS has come so far since i last used it... early A5 engine.


Thank You for any help that might be offered


ever hear the expression once you learn it's hard to forget...
I think learning programming languages as,

I just mastered old school roller skating...
Now they have roller blades, Same wheels, different setup