Re: [Rails-devel] Save file names

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

Next player is the player to do the next move, including Done.
For Rails, this IS the current player.

Adding the previous player (who did the last move) sounds
like a feasible idea, although it is currently not kept anywhere.
To do that consistently will need some work.

In the middle of a turn both names would be identical.

I'll keep this idea in my mind. But first there are somne
new and tricky bugs to fix.

Erik.

> -----Original Message-----
> From: Jim Black [mailto:jim...@ya...] 
> Sent: Monday 23 November 2009 22:09
> To: Development list for Rails: an 18xx game
> Subject: Re: [Rails-devel] Save file names
> 
> > Yes, the special value NEXT_PLAYER will do that.
> > save.filename.suffix=NEXT_PLAYER
> 
> 
> One aside on this current/next player for save files-  ail's 
> notion of  
> current/next player is a little awkward for this, with pbem game,  
> because it strongly depends on whether a player has hit 
> 'Done' yet, or  
> not.
> 
> Once a players hits 'Done', current-player becomes next-player, next- 
> player becomes the-guy-after-that, etc.
> 
> If we were using this for save file names and 
> token/next-player names,  
> we'd have to be pretty disciplined about who presses "Done".
> 
> But, along these lines- I know it's an odd idea, but is there 
> any way  
> to set the default so that it adds suffixes for BOTH current-player  
> (well, more literally- the one who just moved), and, next-player  
> (again more literally, the one who should move right-now) ?
> 
> I'm thinking this might be the ideal way to have our cake and eat-it- 
> too- Tom Dick and Harry were playing 18AL, I might imagine a folder  
> listing like this:
> 
> 1870_T000001_Tom_Dick
> 1870_T000002_Dick_Harry
> 1870_T000001_Harry_Tom
> 1870_T000001_Tom_Harry
> 1870_T000001_Harry_Tom
> 1870_T000001_Dick_Harry
> 
> 
> etc.  The name on the left is the person saving the complete 
> move- the  
> name on the right is the current/next player, who needs to pick that  
> up and move next.  this would be convenient, because it would 
> be easy  
> to BOTH (a) find a specific player's previous moves, (b) see who's  
> move it is next, with Rails help.
> 
> Sorry to be longwinded, just thought I'd mention it.
> 
> Thanks again for all the hard work on rails and this release- 
> all the  
> quick bug fixes, convenient options, etc.  It's great.
> 
> -  jim
> 
> 
>