Reply to thread

Message

<blockquote data-quote="shadzar" data-source="post: 5455339" data-attributes="member: 6667746">But those undefined thing you had a default assumption on and passed along to the players did you not?When you declared there were forests or that objects were made out of wood, you told the players your setting has trees. Not defining the exact trees means nothing as you have defining trees exist.Likewise by not having anyone were this type of jewelry before, you made the default assumption and passed it along to the players that it was not worn or fashionable to do so.Your alteration of that state can when a player or yourself questioned that state.Your default state wasn't necessarily that it wasn't done or not allowed for some reason, just that it hasn't YET been done. That was your established setting. Many of those undefineds form the established setting on common assumptions.While you set the default state of the setting to &quot;none do it&quot; by leaving it as you say &quot;undefined&quot;, it doesn't mean you cannot later alter that state, but you did set the state to begin with even without writing it down.You actively set the state to &quot;undefined&quot; for many things, so you CAN alter them later, by not defining them up front.Just because you haven't decided which walls to paint in your house, doesn't mean the walls are not there to be painted.So when leaving this as a so-called &quot;undefined&quot; element, and not including both options, you really did set the state that people didn't wear flammable jewelry. It is fine to change it for whatever reason so long as your players like the change. But in your setting it didn't happen was the default state, because it didn't. It is just an unwritten part of your setting.</blockquote>

[QUOTE="shadzar, post: 5455339, member: 6667746"] But those undefined thing you had a default assumption on and passed along to the players did you not? When you declared there were forests or that objects were made out of wood, you told the players your setting has trees. Not defining the exact trees means nothing as you have defining trees exist. Likewise by not having anyone were this type of jewelry before, you made the default assumption and passed it along to the players that it was not worn or fashionable to do so. Your alteration of that state can when a player or yourself questioned that state. Your default state wasn't necessarily that it wasn't done or not allowed for some reason, just that it hasn't YET been done. That was your established setting. Many of those undefineds form the established setting on common assumptions. While you set the default state of the setting to "none do it" by leaving it as you say "undefined", it doesn't mean you cannot later alter that state, but you did set the state to begin with even without writing it down. You actively set the state to "undefined" for many things, so you CAN alter them later, by not defining them up front. Just because you haven't decided which walls to paint in your house, doesn't mean the walls are not there to be painted. So when leaving this as a so-called "undefined" element, and not including both options, you really did set the state that people didn't wear flammable jewelry. It is fine to change it for whatever reason so long as your players like the change. But in your setting it didn't happen was the default state, because it didn't. It is just an unwritten part of your setting. [/QUOTE]

Verification