Hi All,
When designing your skill system what is the best way to set it up for casting of skills, i know of 2 ways that would be easiest to use (and most common) so ill throw these out first.
1. the "skill" datum has parent set to obj,so it has icons and mousedrag commands it also has a leftclick command that then launches the "activate" procs
2. have a "card" datum that is parent type obj, which holds a reference to the skill, clicking it just calls the reference's particulars.
I think both are pretty much the same but not to sure.
ID:1239331
 Apr 16 2013, 11:47 pm
|
|
Ter13 wrote:
Neither is optimal. The skill's behavior should be separate from the hud object that you click on. There's no need to have more than one of each skill object unless you are tracking data across multiple uses.> Just store a reference to the type of skill within your hud button to the skill datum that contains the behavior and settings for the action. The part i bolded is kind of what i meant by a card (e.g. 2) it is only there so that associations can be made so i would have 2 lists one for holding the actual skill details such as uses,level, etc then a second list that is never saved which would have the "cards" which are basically the buttons. e.g. 1 is from what i can see the same as what Yut Put has posted in a sense | |
Just store a reference to the type of skill within your hud button to the skill datum that contains the behavior and settings for the action.