Re: [Rails-devel] Players total value (was: Some questions regarding a new release)

[Erik V. <eri...@xs...>]

A few comments below.

> -----Original Message-----
> From: Stefan Frey [mailto:ste...@we...]
> Sent: Tuesday, December 20, 2011 8:07 AM
> To: Development list for Rails: an 18xx game
> Subject: Re: [Rails-devel] Players total value (was: Some questions
regarding
> a new release)
> 
> I thought about this, and used some ideas from accounting (however
> adopted to the 18xx environment).
> 
> What do you think about the following definition to evaluate items for the
> player value displayed in Rails:
> 
> A) Items that have an end game value use that.

All items have an end game value, possibly zero. I understand you mean:
Items that have a non-zero end game value use that. 

> B) Items that will close before end for sure will use the purchase value.

Unless A) also applies?
One problem arises with bankruptcies. A player might think (for instance,
when engineering a bankruptcy) that he owns more end-game value than is
actually the case.

> There is the issue how to evaluate items sold as a bundle:
> Here I would suggest the heuristic that items with value A are deducted
form
> the purchase price first, if a positive value remains it get equally
assigned to
> all items of type B.
> 
> For this we should internally however differentiate between game end
> player value and ongoing current player value: This would allow us easily
to
> choose by game configuration to display end value or current value.

Or both.  That would in any case fix the bankruptcy issue mentioned above.

Erik.