I think I've found a solution. I'll post it here in case anybody else in insterested.
Current AlgorithmExpNeededforNextLevel = ExpNeededforCurrentLevel + (100) CurrentLevel
If I plug it in it seems to work fine..
Level 2
100 = 0 + (100) 1
Level 3
300 = 100 + (100) 2
Level 4
600 = 300 + (100) 3
I've tested it up to level 15, and I haven't seen a problem so I feel safe assuming that it will indefinitely.
There is however another potential problem I'm predicting.
In my project the player 'spends' their experience to purchase player level ups, skill level ups, ability level ups, etc.
I'm not sure how to code and track all of my variable or what my variables should be so that I can keep up with their experience despite the fact they've been 'spending' it.
Quote (Ectasy @ Dec 3 2012 10:07pm)
The equation that models your chart is n(50n - 50)
This also appears to work fine mathematically.
I'm not sure which would be better for the given system I'm trying to implement.
My equation works using a Constant. Which I like, but probably just because in the programming course I have taking my peers always seem to underrate them.
Sure Constants might be unneeded, however they help me a lot when it comes to 'thinking' about my system.
This post was edited by grievance on Dec 3 2012 10:12pm