Started some basic combat system today, although the foundations were actuallyimplemented yesterday night. Now the player can fight with any NPC, until one of them falls dead. The required item/skill subsystem still isnt in place, mostly delayed by my research about the opetimal solution to store the item definitions.
In my previous project, I used an XML file describing the item attributes, not only the RPG related (damage, etc), but also the visual ones, like where does it gets attached. It also had a property system to let objects have complex features, like providing a bonus to stats or skills, inflict/reduce different types of damage, etc. The drawback is that manually editing the XML is tedious and error prone. For this prototype I decided to try something else, like ScriptableObjects. But seems that ScriptableObject is too limited, because it would require a hughe class describing every possible item attribute for all item types. Also, for nested lists I think I will have to implement a custom inspector.
So, I guess I ll have to find a solution for this, or go back to XML. Which, by the way, is not only my choice, other people uses it as well.
In my previous project, I used an XML file describing the item attributes, not only the RPG related (damage, etc), but also the visual ones, like where does it gets attached. It also had a property system to let objects have complex features, like providing a bonus to stats or skills, inflict/reduce different types of damage, etc. The drawback is that manually editing the XML is tedious and error prone. For this prototype I decided to try something else, like ScriptableObjects. But seems that ScriptableObject is too limited, because it would require a hughe class describing every possible item attribute for all item types. Also, for nested lists I think I will have to implement a custom inspector.
So, I guess I ll have to find a solution for this, or go back to XML. Which, by the way, is not only my choice, other people uses it as well.
Comments
Post a Comment