title: AS3 MVC game: Should I separate the data and the game rules in a model?
body: <p>I feel like MVC misses a letter to describe the situation in a game. The model to me seems to consist of two distinct parts:</p>
  
  <ol>
  <li>A group of vars that describe the current game state (these will have setters that send out events on change, and getters so that the view can access what changed)</li>
  <li>The rules of the game that determine what happens once a certain input (i.e. shoot();) has been received by the controller (these will update the group of vars as deemed appropriate)</li>
  </ol>
  
  <p>The view will exclusively be reading from 1 while the controller will be exclusively communicating with 2. This is why I make the distinction and want to divide them up into class1 and class2.</p>
  
  <p><strong>My questions:</strong></p>
  
  <ul>
  <li>I am unsure if I should be making this distinction, since I haven't seen it anywhere.</li>
  <li>If I should; should I make two separate classes, or should I extend class1 with class2?</li>
  <li>Finally, I am having trouble making sure that only class2 (and not the view) can change the variables in class1 (while still being able to send out an event when a value changes). Any suggestions?</li>
  </ul>