How about you add an additional challenge every 10 levels, with a maximum of a 100 levels?

Maybe even just 50 levels, if additions are substantial: you don't wanna drown yourself with more work.

Yes: you have less levels, but there's more content to 'em. This will also motivate the player to keep on playing to find out what the next (or extra) challenge will be.

As your game is fast, players might catch on to what is happening faster and stop playing the game as they already know what's around the next corner.

My two pence:D

Ashley "( ' O ' )" OH! I thought it was part of "The Master Plan", and that you had to answer to people in expensive executive leather chairs with fat cigars between their teeth.

My bad "(^.^)"

Ashley is it really viable translating C3 to Dutch?

I mean "proper", "pure" and "correct" Dutch?

A country that uses freight ships loaded with English terminology?

I mean, talk about commitment (@.@)

LaDestitute Some investment (^-^) !

Wait, no refund or replacement on the PSU (@.@) ? No love from the vendor?

Ontrac has a "1 star" rating.

So what did they do to your PSU? Slam dunk it on the front porch?

Good that you're feeling better.

Sometimes one forgets his/hers humanity, gotta take care of yourself (^o^) !

Cool !

How much did that set you back ?

Are you feeling better LaDestitute by the way? (Reference your topic: Having doubts and stress as a developer.)

Same here. Have the tick the box, otherwise I log out. Not complaining, just "Meh, odd.".

I asked my community which devices they are using and then focused my application over a few makes and models specifications. Just to make sure that when the app was published it would work on the majority of the game's fans gadgets.

Keeping the community up to speed about tested models and those to come left the community less likely to leave negative comments, and I would apologize for the waiting game.

Maybe I was lazy by doing this, but feedback would surprisingly be centered around a specific range of Samsung Smartphones. I would have been wasting time and resources trying to get my app going for models of phones and OS's NOBODY in my close ranged community was using.

More like strategically seizing "Smartphone and OS's" terrain little by little focusing on the most obtainable one first.

But, yeah, that's me.

I would use the behaviors: Bullet and Line Of Sight. If using multiple objects: add these objects to a Family and apply the behaviors to that Family. It's my understanding that using Physics unnecessarily may be wasting the PC's CPU. Keep events as simple as possible. However I'm not a pro and there's probably more fine tuned ways.

Hope this helped you in some way.

Have you tried making objects affected by gravity, when in in range of a planet, set angle and speed towards the planet?

HAHAHA (=^o^=), bottem of the page.

Well ('o') I've managed to get an old PC working again running W7. As for my broken AIO, I'll be taking jojoe advice and use it for Mint to practice and leave room to test/run other OS.

At least I can proceed with C2 projects as well graphics and music. Has been a while since I played a good game too.

Cheers everyone (^.^) !