Reply to thread

Message

<blockquote data-quote="Umbran" data-source="post: 8365422" data-attributes="member: 177">Yes, but for example, &quot;class feature&quot; is not a single design object.&nbsp; As an example, some class features are a bonus on a specific die roll.&nbsp; Other class features are creatures with their own stat blocks and their own abilities, that are dynamically dependent on the character.&nbsp; In terms of computer system design, those two features are nothing alike.&nbsp; And you can imagine game designs (like, psionics that work off a psionic &quot;power points&quot; system, that lots of people really wanted), that are not on your list at all.&nbsp; When classes can have features of arbitrary design, the software isn't going to be able to hendle them all with aplomb.Oh, goodness gracious, &quot;it is finite, so it is doable&quot; is incredibly misleading.&nbsp; Yes, with sufficient code, any piece of data can be gotten to any other place in the system you need it.&nbsp; But that's not the whole story.&nbsp; For example, you need to do that in a way that is secure, performant, and affordable at the scale of users you are working with today.&nbsp; When the number of users rises, the design you chose for the level of perfomance and economy of the past is apt to fail, but changing fundamental architecture to scale up is expensive and time consuming.</blockquote>

[QUOTE="Umbran, post: 8365422, member: 177"] Yes, but for example, "class feature" is not a single design object. As an example, some class features are a bonus on a specific die roll. Other class features are creatures with their own stat blocks and their own abilities, that are dynamically dependent on the character. In terms of computer system design, those two features are [I]nothing alike[/I]. And you can imagine game designs (like, psionics that work off a psionic "power points" system, that lots of people really wanted), that are not on your list at all. When classes can have features of arbitrary design, the software isn't going to be able to hendle them all with aplomb. Oh, goodness gracious, "it is finite, so it is doable" is incredibly misleading. Yes, with sufficient code, any piece of data can be gotten to any other place in the system you need it. But that's not the whole story. For example, you need to do that in a way that is secure, performant, and affordable at the scale of users you are working with today. When the number of users rises, the design you chose for the level of perfomance and economy of the past is apt to fail, but changing fundamental architecture to scale up is expensive and time consuming. [/QUOTE]

Verification