> On Oct 25, 2017, at 6:15 PM, Nic Evans <nich...@gmail.com> wrote: > > On 10/25/17 16:30, Kerim Aydin wrote: >> >> Secondarily, I'd like to remove actions that require knowing the whole >> gamestate (of those currencies) perfectly and fluctuates on a weekly >> basis: setting FV in particular. If "the value of everything" changes >> with an officer's announcement and requires prefect knowledge, having it >> happen weekly means either the Officer has to be very consistent in >> timing, and be perfect, or whenever e misses a week or makes errors, >> peoples' strategies for the week go out the window, and literally half >> our play time is correcting mistakes. > > I think this is the central failing point of this economy. We've made > several patches to transparency and calculation, but ultimately what we > have is a system that allows completely decentralized instant actions > but each of those actions have a global effect. It might work fine as a > computer game, but it's not suited to something where everything is > mostly done by people. O has done absolutely astounding work, and it > still results in regular mistakes.
This is one of the motivations behind trying to automate some of my recordkeeping in a generic, extensible way, to be honest. There’s a lot of being the Treasuror or the Surveyor that are mechanical past the point of noticing that a message contains a given action. Working out the dependencies and resolving mistakes is, at least in principle, amenable to machinery, and I’m acutely aware of the sheer volume of correction mail I send out these days. -o
signature.asc
Description: Message signed with OpenPGP
