Reply to thread

Message

<blockquote data-quote="BeerSkunk" data-source="post: 348016" data-attributes="member: 6915">N-Body ConceptI've been focusing on this very problem with my Campaign Manager software.&nbsp; How to take into account all possible additions to a character without the need to re-compile the software.Let me give some clarification on my terms:Object - Anything we want to model (town, house, charater, etc)Body - An Object that is an attribute for another ObjectStarting with Jamis' original proposal of an N-Bodied Object, I think it makes sense to look at our generic Object as nothing more than a collection of N-Bodies that describe it.&nbsp; Each of those N-Bodies also has N-Bodies that describe them as well.&nbsp; For conceptual purposes, think of an infinitely expanding tree where each Object is represented by a node on that tree and has N-children(Bodies) that describe its attributes.Now we have a generic Object with a host (N) of other Objects that are used to describe it.&nbsp; There are absolutely no relationships between the N-Bodies that make up our Object.&nbsp; This is exactly what we want.&nbsp; In order to have relationships such as cause/effect between our Bodies, we would have to enforce some sort of rules to govern those relationships, which we don't want to do.The rules used to describe the relationship between the N-Bodies of an Object can be seen as a View of our data (Object).&nbsp; For instance, D&amp;D is one way of viewing D20 character data.&nbsp; Star Wars is another View of D20 character data.&nbsp; What a particular View does is interpret the relationships between the N-Bodies of an object and enforce those relationships.So, what we have are actually two systems.&nbsp; One, the generic character generator which simply spits out data about an Object.&nbsp; And second, we have a View of that data that comprises the game rules for interpreting that data.Those are my thoughts on the matter.&nbsp; Scrambled and served hot. <img src="https://cdn.jsdelivr.net/joypixels/assets/8.0/png/unicode/64/1f642.png" class="smilie smilie--emoji" loading="lazy" width="64" height="64" alt=":)" title="Smile&nbsp; &nbsp; :)"&nbsp; data-smilie="1"data-shortname=":)" /></blockquote>

[QUOTE="BeerSkunk, post: 348016, member: 6915"] [b]N-Body Concept[/b] I've been focusing on this very problem with my Campaign Manager software. How to take into account all possible additions to a character without the need to re-compile the software. Let me give some clarification on my terms: Object - Anything we want to model (town, house, charater, etc) Body - An Object that is an attribute for another Object Starting with Jamis' original proposal of an N-Bodied Object, I think it makes sense to look at our generic Object as nothing more than a collection of N-Bodies that describe it. Each of those N-Bodies also has N-Bodies that describe them as well. For conceptual purposes, think of an infinitely expanding tree where each Object is represented by a node on that tree and has N-children(Bodies) that describe its attributes. Now we have a generic Object with a host (N) of other Objects that are used to describe it. There are absolutely no relationships between the N-Bodies that make up our Object. This is exactly what we want. In order to have relationships such as cause/effect between our Bodies, we would have to enforce some sort of rules to govern those relationships, which we don't want to do. The rules used to describe the relationship between the N-Bodies of an Object can be seen as a View of our data (Object). For instance, D&D is one way of viewing D20 character data. Star Wars is another View of D20 character data. What a particular View does is interpret the relationships between the N-Bodies of an object and enforce those relationships. So, what we have are actually two systems. One, the generic character generator which simply spits out data about an Object. And second, we have a View of that data that comprises the game rules for interpreting that data. Those are my thoughts on the matter. Scrambled and served hot. :) [/QUOTE]

Verification