BlogNomic: The First Dynasty of Desertfrog

I don’t think I agree with this definition.

I have since quibbles with the word ‘persistent’, which I think means something different technically va colloquially, but most importantly for me this definition misses an important factor that differentiates a variable from a non-variable: a defined method by which it can be changed. (That element is complex, by the way, as I think that player names are non-variable despite there being a defined method by which they can be changed…)

Here’s my understanding of variables in the context of BN (only listing the discrepancies)
- They need not to be persistent. E.g., the W, G and N used in the Build action. Some variables are only meaningful within a scope and every time we enter that scope the value starts from default again (instead of carrying over).
- Currently, reading from the Variables and Numbers rule in the Appendix, the bullet “If a game variable has a default value but no defined starting value…” only recognises numbers, strings, sets and lists as valid variable types.
- I also mostly agree with Josh, in that variables must be able to be changed. However, I don’t think we need a defined way to change it - a variable is just a word or phrase that can change, like “the most recent Engineer who performed an Inspection”. I also take the stance that Player Names are variables for consistency.

I think the shared contention from the two of you is interesting, but I’m not sure I agree that a defined method of change is required for a variable! If we write a rule that says “All players have a publicly tracked amount of Health, which is a number defaulting to 0,” and nothing else, is that not then a variable? I’d argue that between “a variable is an element of gamestate” and “The Ruleset and Gamestate can only be altered in manners specified by the Ruleset,” that’s enough to imply variability.

So the question still boils down to which of the following are valid variables
- “Building Number”
- “Expertise” (of an Engineer)
- “Name of the Engineer”
- “the most recent Engineer who performed an Inspection” (nothing in the Ruleset specifies how it changes but its name defines its contents)
- “the set of Engineers” (a group of entity with a certain property that a Rule can add to or remove from, is well-defined, but no one knows what it initialised as nor what values it may take (I guess its values are Engineers, but that’s circular definition))
It gets very confusing. The more I think about this the more it confuses me, but I guess that’s what makes this Proposal purposeful: to clarify.

Also, I just wanna quickly mention a new idea too. We could implement a type system so that our variables have well-defined types that can default to what the respective types default to. (New types needs to be defined in Dynastic Rules?)

BlogNomic programming language!

from me on this as I don’t think we got close to a consensus definition

I’m performing an Inspection.

“A variable is [an]... element… which may belong to an entity”. Not sure this clarifies things really.