Nadorrano
commented
9 years ago Hi, I have little time in this period and I didn't follow the IRC discussion. I apologize if this has already been discussed.
Point 2: This is a problem that has to be solved at a global (archetype) level, not just for skills and spells. Can't we make archetypes as properties? so that archetype data is stored in modules and not in database? In this way if, in the future, we want to add/remove skills we can do it in the archetype module and all characters will be affected automatically. This is also valid for race, we can add/remove slots/limbs without re-initialize all characters. Anyone has an idea of the compared efficency between: "load a class from db" and "reinitialize the class" (at every call)?
Point 3:
I think we can use commands for skills, in order to mantain a good versatility (in parsing, for instance).
For spells we can make a single cast command and a library of functions, something like: spell(caller, target, **kwargs).
My two cents.
ergodicbreak
abbacode
Griatch
whitenoiseoss
feend78
Hi all,
Creating this so we can have clarity around how the ability system will work.
Objectives from IRC discussion
If this is incorrect, please advise and I'll update this post.
Questions
Decision Point 1: Learning/Unlearning Skills
Should we be introducing the basic concept of learning/unlearning skills as part of the initial Ainneve role out? Is it an important core feature that people who fork Ainneve in the future will likely use, i.e. allow players to learn a new skill via a 'trainer mob' or purchase new 'spellbooks' etc.
Decision Point 2: How to store abilities
How do we actual store skills and spells on a character? The logical conclusion would be to create a new attribute on the character class, i.e.
self.db.skills = {} self.db.spells ={}
New Skill and Spell classes can be created which inherit from a parent Ability Class. These objects can then be assigned for each ability and stored under the character class. The problem I can see with this system is how you maintain it moving forward. Each object that is initialized using this approach is a unique instances assigned to each player. There is no simple and clean method that allows us to make tweaks or modifications to skills or spells and have these propagate to all players.
Decision Point 3: Data driven vs de-centralised
How do we structure the code? The two options that have been discussed are data driven and decentralization.
Data driven implying that we have a skill and spell database where we store all the the core attributes. This would include things like descriptions, cast/use messages, modifiers, delay_on use settings etc. When coding new skills and spells, you can make reference back to the database to pull key information.
De-centralised:
A class is defined for each skill and spell and all the relevant attributes are hardcoded within the relevant python source file.
Other
Please post any other items that need to be discussed for abilities and I'll update the top post to reflect the current position.