SPHERE O PATH

WORK IN PROGRESS.  PLAYABLE TO LEVEL  8.

LEVEL 9 was  just started

LEVEL 10 was use for various test  so it pretty much a empty level.

Major need of work:

It definitely need more level. The game difficulty  per level is so gradual that  it feel like a tutorial until level 5. So yeah. It totally need more level.

As of right now there's sound that stick  even tho  it should of died.
Will make sure to end  this none sense in the next build.

StatsGUI  is not accurate on death player, Red code on death player and operator on death player. Other stats in the Stats GUI should work as intended.  No impact in gameplay. I probably will modify the look of it so it's more understandable .

Menu with settings but only the option for fullscreen work.(The  option for fullscreen is not enable and you start fullscreen so there's that to rectify) It a mess. Don't bother.

Music  but nothing to be hype about.  Use  various music i made over the years. I messed up the speed  so everything sound  a little weird. I made a mute button just in case .(In Pause Menu)

DESCRIPTION CORE MECHANIC:

SPHERE O PATH IS A HYBRID RUNNER GAME. YOU PLAY AS A SPHERE AND YOU  TRAVERSE YOUR WAY TO THE END.

Instead of jumping over obstacles  vertically  or dodging obstacles horizontally. The player will fall continuously and need to dodge obstacles in all axis.
You may halt the continuous fall by floating.(Ability)
Almost forgot to mention. The continuous  fall act like gravity will do. The momentum will keep growing gaining speed in free fall.  To  survive the player will have no choice but to use float to survive and/or various else ability.

HOW TO PLAY:

Movement Control with W,A,S,D

Space Bar to Float

LeftShift for Turbo

Slowdown time with F

Rewind time with R

Change Camera Distance with C or  Scroll Wheel

Change Style of  Follow Camera with V Classic/Pro

Q and E do nothing as of now. But my goal is to add a new Ability
if you got any suggestions on what should that ability is comment it down below.

BASIC GAMEPLAY:

Avoid getting in contact with red code or operators. Finish the level before time run out.

COMPLEX GAMEPLAY :

the  timer countdown.

I was not to keen on making this game with a scoring system in mind.

So i made something different with a countdown system that change overtime with some RNG involve.

Death:

Death progression on countdown.

Dying for the first time will activate a countdown of 5 minutes.

Dying 2 to 5 time will reduce the countdown time for 15 seconds each death.

Dying 6 to 10 time will reduce the countdown time for 30 seconds each death.

Dying more then 11 time will reduce the countdown time for 1 minute each death.

Particle Hit:

Every particle that hit a red code have a chance to do (only if countdown was activated(1 death))

It will take 5 seconds before every chance will begin. Only one demand at a time. If the red code denied entry it will be ready for another chance.

70% chance to denied entry inside Red code. Reducing time for 5 seconds.

Ready for another attack.

20% chance to get entry inside Red code. Will self destruct and Add time for 15 seconds.

10% chance to get entry inside Red code but the system defense got inform of the deed.

Sending a Operator to replace the self destructed Red code and Add time for 10 seconds.

On Contact With:

Contact With Red code will self destruct contacted Red code and reduce time for 15 seconds.

Contact With Operator will self destruct contacted Operator and reduce time for 15 seconds.

Operator on Operators. Will self destruct and Add time for 15 seconds each Operator self destruction.

Operator on Redcodes. Will Self destruct and Add time for 15 seconds each Red code and Operator self destruction.

Operator on Wall, Bounce and Glue. Will Self destruct and Add time for 15 seconds.

Why a Runner Game:

I know the runner genre is over saturate . The game was mostly created to get up to speed with C# without having to search every little code i wanted to add. I used Brackeys tutorial on the runner game for the base project.  It was easier to add new  idea over the same project following  other tutorial. I tried creating project before  looking at Brackeys tutorial to no avail. I kept getting stuck in the smallest detail.

After getting the base started something weird happens. My mind could not comprehend the code in front me. I couldn't even see what my script did and why. I was  in a blank state. After revisiting all my script one by one and understood what was happening. It was a much easier ride to push more idea into the game without some invisible hand  telling me what should i do next.

Since the idea wasn't really about making a game but learning how to make a game.

Ill keep  working on it hence why it still in  In development  to keep me updated while i start new projects.

IN DEVELOPMENT:

Will it differ from what it is now. Highly doubt it.  It will be more about making it bug free as possible, make more level  and finish the settings menu. I may add new thing but the core mechanic/gameplay & models wont change.

Don't be afraid to give suggestions . If i find the idea excellent  i could change my mind on not changing any core mechanic/gameplay or models.

If my game is publish online  for the most part is to receive objective criticism. For me that is a necessary step and is really important. It give me perspective on how  to keep going with my projects.

GOOD LUCK!
AND  HAVE FUN!