I'm not trying to take credit for any of that. It's all blatantly stolen. I was just trying to flesh out the outline of what to do with G's ideas.
-Aris On Tue, Sep 13, 2016 at 11:44 PM, Aris Merchant < thoughtsoflifeandligh...@gmail.com> wrote: > Thanks. Okay, so it seems to me like it might be a good idea to bring back > some type of objects system, in order to provide a framework for future > expansion. I see three options: > 1. Pure currency (Based on switches or independent) > 2. Pure objects/property/assets (currency like any other, with a few extra > rules) > 3. Hybrid > > I'd go for some sort of hybrid system. The best way to do this is probably > some sort of inheritance scheme. The way I'd go about this is that > property/assets inherits from objects, and currency inherits from objects. > Trying to do this all with switches would definitely be forced. One could > argue that you'd never need objects that aren't property, but it could come > in handy eventually. I'd define each one in it's own rule, each with a > clause saying that it would become inoperative if something it inherits > from disappears and isn't replaced. One wonders if one should allow for > nontransferable property? Probably getting way ahead of myself with all > this. It's not like I'm talking about throwing away the current econ draft, > just heavily modifying it. Thoughts? > > -Aris > > > On Tue, Sep 13, 2016 at 2:00 PM, Kerim Aydin <ke...@u.washington.edu> > wrote: > >> >> >> >> On Mon, 12 Sep 2016, Aris Merchant wrote: >> >> > Okay, I'm not sure wether I'm supposed to ask this or find it >> > myself, but when did this objects system exist? Or how did it work? >> > Sounds like it might be a good idea. Possibly. Okay, I'm not really >> > sure how it is, but it sounds decent. Another question is why we >> > got rid of it. Was it just no longer in use, or was it causing some >> > sort of problem? >> >> First and foremost, welcome to the game, Aris! >> >> Chatting about this stuff is something we enjoy, and we all remember >> different bits of history, and the archives aren't organized, so >> definitely, always ask, bring up, discuss... >> >> The rules are constantly being tweaked and often "cause problems" and >> get fixed, but occasionally we just get bored with a whole set of >> rules (or just stop using some things for a while) and repeal systems >> so they can be re-invented later. "Objects" have gone through a few >> rounds of that. >> >> Here's two random snapshots of the past (I found these by browsing >> the Rulesets in the mailing list archives). In 2010 we had "Assets". >> In 2003 we had "Property". In the 2003 version, notice how regulated >> "Notices of Transfer" were (that was the "pragmatic" style of the >> time we were talking about earlier). >> >> -G. >> >> ===================================================================== >> >> SEPTEMBER 2010 >> >> Rule 2166/15 (Power=2) >> Assets >> >> An asset is an entity defined as such by a rule or contest >> (hereafter its backing document), and existing solely because >> its backing document defines its existence. >> >> Each asset has exactly one owner. If an asset would otherwise >> lack an owner, it is owned by the Lost and Found Department. If >> an asset's backing document restricts its ownership to a class >> of entities, then that asset CANNOT be gained by or transferred >> to an entity outside that class, and is transferred to the Lost >> and Found Department if it is owned by an entity outside that >> class. If an asset is owned by the Lost and Found department >> any player CAN transfer or destroy it without objection. >> >> The Lost and Found department may own any asset, and have assets >> transferred to and from it, regardless of the asset's backing >> document or any Rule, Rules to the contrary notwithstanding. >> >> The recordkeepor of a class of assets is the entity (if any) >> defined as such by, and bound by, its backing document. That >> entity's report includes a list of all instances of that class >> and their owners. This portion of that entity's report is >> self-ratifying. >> >> An asset whose backing document is not a rule generally CAN be >> created by its recordkeepor by announcement, subject to >> modification by its backing document. To "gain" an asset is to >> have it created in one's possession; to "award" an asset to an >> entity is to create it in that entity's possession. >> >> An asset generally CAN be destroyed by its owner by >> announcement, and an asset owned by the Lost and Found >> Department generally CAN be destroyed by its recordkeepor by >> announcement, subject to modification by its backing document. >> To "lose" (syn. "spend") an asset is to have it destroyed from >> one's possession; to "revoke" an asset from an entity is to >> destroy it from that entity's possession. >> >> An asset generally CAN be transferred by its owner to another >> entity by announcement, subject to modification by its backing >> document. A fixed asset is one defined as such by its backing >> document, and CANNOT be transferred; any other asset is liquid. >> >> A currency is a class of asset defined as such by its backing >> document. Instances of a currency with the same owner are >> fungible. >> >> ===================================================================== >> >> APRIL 2003 >> >> Rule 1942/2 (Power=1) >> Property >> >> A property is an entity which the rules permit to be possessed >> by another entity. The term "possess" refers to the legal >> status of possessing a property; the terms "possessor" and >> "owner" are synonyms, as are "possess" and "own". Individual >> properties may not be created or destroyed, or their ownership >> changed, except in accordance with the rules. >> >> Each property shall have a recordkeepor, which is a player >> required to maintain a record of who owns that property. The >> Treasuror is the recordkeepor for each property that would >> otherwise have no recordkeepor. >> >> If one of the official duties of an officer is to be the >> recordkeepor of a property, then eir Weekly Report shall include >> this record and any changes thereto since the last posting of >> eir Report. >> >> --------------------------------------------------------------------- >> >> Rule 1467/7 (Power=1) >> Definition of a Currency >> >> A Currency is a category of entities established by the Rules. >> Each instance of a Currency is a Property. Instances of a given >> Currency are fungible. The size of a single instance, or >> "unit", of a given Currency is its Minimum Unit Quantity (MUQ). >> Individual units of a Currency cannot be divided; therefore, >> the final result of all computations involving numbers of units >> of Currency shall be rounded off to the nearest integral >> multiple of its MUQ. >> >> Unless otherwise specified, the MUQ of a Currency is one (1). >> >> Since units of Currency are fungible, it is not necessary for >> the Recordkeepor of a Currency to track the individual >> ownership of each unit; rather, it is sufficient to maintain a >> record of the total number of units possessed by each entity >> which possesses any number of units of that Currency. >> >> --------------------------------------------------------------------- >> >> Rule 1598/12 (Power=1) >> Property Transfers >> >> (a) A Notice of Transfer is a message which sets forth the >> intent to transfer one or more Properties from one entity >> (the "transferor") to some other entity (the "transferee"). >> >> (b) A valid Notice of Transfer must additionally: >> (1) specify one or more Properties all of which are owned by >> the transferor; and >> (2) be sent by the Executor of the transferor, or by a >> Limited Executor of the transferor with the authority to >> execute transfers on behalf of that entity with respect >> to all of the Properties involved. >> >> (c) A transfer of a Property occurs only when its Recordkeepor >> receives a valid Notice of Transfer. >> >> (d) The effect of a transfer of Properties is to cause the >> transferor to cease to possess the Properties transferred, >> and simultaneously to cause the transferee to possess them. >> >> (e) The Recordkeepor of a Property shall maintain a record of >> all transfers of that Property. E shall retain a record of >> each Notice of Transfer which e receives (whether valid or >> not) involving that Property. E shall retain this record of >> each Notice of Transfer for at least four weeks after its >> receipt. >> >> (f) If the transferor transfers Property to the transferee with >> the purpose of satisfying a debt, or of paying the Fee >> associated with performing an action, but the debt does not >> exist, or the action is not successfully performed, then the >> transferor may publicly demand the return of the Property. >> The effect of such a demand is to cause the transferee to >> incur a debt to the transferor for the Property transferred. >> >> ===================================================================== >> >> >> >> >> >
