You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There should be a system for the player gaining experience and leveling up stats. Perhaps, in general, entities will be assigned a level depending on the total of the stats?
One possible solution for the player is a class system. The player's class would contain the following:
A function that defines the amount of experience needed to reach a level. Traditionally, such a function would be exponential.
An array of hash objects (like Equippable's stat_change) that define the change in stats at each level. Alternatively, a linear progression would be simpler but more limiting.
Other neat things.
To be continued...
Send pull requests to the level-system branch.
The text was updated successfully, but these errors were encountered:
Some other thoughts on how this might be implemented.
Somewhere in the code a constant could be defined that describes the various level tiers. EXPERIENCE_LEVELS = {1: 100, 2: 500, 3: 1200, 4: 2500, etc., etc.}
Then you could keep a running tally of experience points and run checks when trying to purchase a weapon, or perform some sort of action to see if the player's current level is greater than or equal to the level necessary to own a weapon or perform a specific action.
Also, when a player fights a monster and wins, exp goes up, but if player flees or dies, they lose exp. This way a player's level could stay fluid throughout the game.
Just some thoughts. I'm still familiarizing myself with goby and how all its parts work together.
Hi I saw the help wanted tag on this and thought I'd try a hand at how this could be implemented. I'll probably have some questions about the range of stat increases going through.
There should be a system for the player gaining experience and leveling up stats. Perhaps, in general, entities will be assigned a level depending on the total of the stats?
One possible solution for the player is a class system. The player's class would contain the following:
Equippable
'sstat_change
) that define the change in stats at each level. Alternatively, a linear progression would be simpler but more limiting.To be continued...
Send pull requests to the
level-system
branch.The text was updated successfully, but these errors were encountered: