rails-devel — List for discussion of Rails development

Re: [Rails-devel] Problem with Revenue Calculation

[John D. G. <jd...@di...>]

On 2011-10-28 16:08, Bob Probst wrote:
> If you see the attached screenshot, you'll see that B&O has 2 trains and legal runs but the Maps panel shows Revenue set to $0 and the Payout reads "No Trains".

The payout *should* read "No train" (assuming that's what it was last round)
until you click "Pay Out" or "Withhold" for the current turn.

Re: [Rails-devel] Problem with Revenue Calculation

[Rick W. <wes...@pu...>]

Maybe you can look at your 18xx.log file and see if you find the following:

Game option RevenueCalculation set to Suggest


If not set to Suggest then what did you set it to?


On Oct 28, 2011, at 7:08 PM, Bob Probst wrote:

> I've recently started using Rails 1.5.1 in a game of 1830.  and I've noticed that it no longer calculates revenues for me.
> 
> If you see the attached screenshot, you'll see that B&O has 2 trains and legal runs but the Maps panel shows Revenue set to $0 and the Payout reads "No Trains".
> 
> I can figure out the revenue manually, enter it and everything works fine but I really enjoyed the manual calculations.
> 
> Is this an issue that can be fixed in a configuration file? or is it a platform issue?
> 
> 
> I'm running this on Ubuntu Linux 10.04 LTS Lucid Lynx and using OpenJDK Java 6 Runtime
> 
> Thanks for any help you can provide.
> <Screenshot-Rails: Map, Operating Round 2.1 (1 of 1).png>------------------------------------------------------------------------------
> Get your Android app more play: Bring it to the BlackBerry PlayBook 
> in minutes. BlackBerry App World&#153; now supports Android&#153; Apps 
> for the BlackBerry&reg; PlayBook&#153;. Discover just how easy and simple 
> it is! http://p.sf.net/sfu/android-dev2dev
> _______________________________________________
> Rails-devel mailing list
> Rai...@li...
> https://lists.sourceforge.net/lists/listinfo/rails-devel

Re: [Rails-devel] 1825 half-tiles

[John D. G. <jd...@di...>]

On 2011-10-28 13:22, Erik Vos wrote:
> However, the question arises how to interpret the rule that "Tiles may be
> placed so that a railway terminates against the edge of the board or against
> the side of an incomplete hexag"  in some specific cases where laying track
> would not be allowed if the adjacent board was actually present.  For Unit
> 1, this refers to the Q row hexes, of which only the southernmost corner is
> just visible on the Unit1 game board.  If taken literally, the cited rule
> would allow track lays against all edges of the Q row hexes if Unit2/R3 are
> absent.  
> 
> However, if both Unit2 and Kit R3 are present, hex Q11 (Wolverton) would be
> only reachable from the SE, and hex Q21 (The Wash, i.e. sea) not at all.
> And that is how I had implemented it also for the case that Unit2/R3 are
> absent (I only vaguely remember that we might have had some discussion about
> this issue).
> 
> My current preference is to use a half-tile on hex Q11 (to which therefore
> track can be laid from both the SW and SE directions), and to omit it on hex
> Q21 (which therefore cannot be laid any track against).  To replicate the
> current behaviour, I would have to omit the half-tile from Q11, and keep
> using the existing 'open' attribute instead, so that Q11 can only be laid
> track against from the SE.
> 
> Any opinions?

What does any player have to gain from laying dead-end track?  Do people do it
to use up a critical tile?  To prevent someone else from connecting that line
to a destination?

The only reason I can see wanting to do it is to enable a player to place a
city tile with lots of exits at the edge of the board even though some of the
exits run off the board (thus avoiding the need to include tiles with some
blank sides, such as 1870's #170 "P" cities, in the tile mix).  In which case
either a narrow rule allowing just those city-tile lays, or a board that has
dead-end tracks adjoining the unused sides of those city hexes, would have
made more sense than the general rule.

Re: [Rails-devel] 1825 half-tiles

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

I'm including these half-tiles into 1825 Unit 1, and it basically works.
As expected, it turns out, that adding these half-tiles makes the existing
"open" attributes redundant. This attribute achieves the same thing: that
track can be laid towards the board edge.

However, the question arises how to interpret the rule that "Tiles may be
placed so that a railway terminates against the edge of the board or against
the side of an incomplete hexag"  in some specific cases where laying track
would not be allowed if the adjacent board was actually present.  For Unit
1, this refers to the Q row hexes, of which only the southernmost corner is
just visible on the Unit1 game board.  If taken literally, the cited rule
would allow track lays against all edges of the Q row hexes if Unit2/R3 are
absent.  

However, if both Unit2 and Kit R3 are present, hex Q11 (Wolverton) would be
only reachable from the SE, and hex Q21 (The Wash, i.e. sea) not at all.
And that is how I had implemented it also for the case that Unit2/R3 are
absent (I only vaguely remember that we might have had some discussion about
this issue).

My current preference is to use a half-tile on hex Q11 (to which therefore
track can be laid from both the SW and SE directions), and to omit it on hex
Q21 (which therefore cannot be laid any track against).  To replicate the
current behaviour, I would have to omit the half-tile from Q11, and keep
using the existing 'open' attribute instead, so that Q11 can only be laid
track against from the SE.

Any opinions?

Erik.

> -----Original Message-----
> From: Erik Vos [mailto:eri...@xs...]
> Sent: Friday, October 28, 2011 12:52 PM
> To: 'Development list for Rails: an 18xx game'
> Subject: Re: [Rails-devel] 1825 half-tiles
> 
> Thanks, Stefan. As you say, a visual cue might be helpful.
> 
> There hasn't been any significant development on 1825 after I created the
> maps.  Most of the XML (except for Unit 1) still has to be done.
> I did already prepare that to some extent by adding quantity increments as
a
> configuration option.
> 
> Erik.
> 
> > -----Original Message-----
> > From: Stefan Frey [mailto:ste...@we...]
> > Sent: Friday, October 28, 2011 10:39 AM
> > To: 'Development list for Rails: an 18xx game'
> > Subject: [Rails-devel] 1825 half-tiles
> >
> > Actually I found this mail sitting in my draft folder.
> > It intended to provide half hexes for 1825.
> > I do not know if this is still required, I lost track on the progress
> > of
> 1825 lately
> > (if there has been any).
> > Stefan
> >
> >
> > Some time ago I edited the SVG files of the empty hex to create the
> > half
> hex,
> > but forgot to send them out. I know that the current support of 1825
> already
> > allows to lay track off the map, but there is no visual hint, where
> > this
> is
> > possible. So I wonder if they could be added.
> > My experience now that for small changes it is actually much easier to
> edit
> > the SVG directly than using Inkscape (the edit took hardly more time
> > than writing this mail)
> 
> 
>
----------------------------------------------------------------------------
--
> The demand for IT networking professionals continues to grow, and the
> demand for specialized networking skills is growing even more rapidly.
> Take a complimentary Learning@Cisco Self-Assessment and learn about
> Cisco certifications, training, and career opportunities.
> http://p.sf.net/sfu/cisco-dev2dev
> _______________________________________________
> Rails-devel mailing list
> Rai...@li...
> https://lists.sourceforge.net/lists/listinfo/rails-devel

[Rails-devel] 18TN -- tile problems

[Rick W. <wes...@pu...>]

My gaming buddy and I are just finishing our first game of 18TN.  We notice that the grey tile (#600) can not be laid; it is an upgrade from tile #170.  Also tile #170 is showing 168 available tiles with 2 on the board.


-- Rick

Re: [Rails-devel] 1825 half-tiles

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

Thanks, Stefan. As you say, a visual cue might be helpful.

There hasn't been any significant development on 1825 after I created the
maps.  Most of the XML (except for Unit 1) still has to be done.
I did already prepare that to some extent by adding quantity increments as a
configuration option.

Erik.

> -----Original Message-----
> From: Stefan Frey [mailto:ste...@we...]
> Sent: Friday, October 28, 2011 10:39 AM
> To: 'Development list for Rails: an 18xx game'
> Subject: [Rails-devel] 1825 half-tiles
> 
> Actually I found this mail sitting in my draft folder.
> It intended to provide half hexes for 1825.
> I do not know if this is still required, I lost track on the progress of
1825 lately
> (if there has been any).
> Stefan
> 
> 
> Some time ago I edited the SVG files of the empty hex to create the half
hex,
> but forgot to send them out. I know that the current support of 1825
already
> allows to lay track off the map, but there is no visual hint, where this
is
> possible. So I wonder if they could be added.
> My experience now that for small changes it is actually much easier to
edit
> the SVG directly than using Inkscape (the edit took hardly more time than
> writing this mail)

[Rails-devel] Configuring game options (was: 18EU game option: unlimited plain track)

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

Stefan,

Thanks for the reminder.  We should document it somewhere...

In relation to the new game option we have just added, I have been thinking
how we could rationalize option configuration.  
I see two main issues:

1. The need to configure each option twice.
Historically, this has been caused by the (IMHO unfortunate) decision to
combine game selection and option selection in one overall game setup
window. Originally we had two separate windows. 
In the existing game initialization procedure, I think the best approach to
remove the resulting duplication would be to remove the option tags from
both GamesList.xml and Game.xml, and put these into a separate Options.xml
file per game.

2. The need to configure global options separately for each game.
I have long pondered about ways to specify "global" options only once. I
believe the following options fall into this category:
RouteAwareness
RevenueCalculation
UnlimitedTiles
SeparateSalesAtSamePrice
NoMapMode (perhaps not really, as this option may require game-specific
code, IIRC).
If (and only if) we are going to refactor option configuration into separate
XML files, we could as well collect such global options into one global
GameOptions.xml file.  Such global options could still be overridden in
game-specific option files (including invalidating such options, if
possible).

My proposal includes:
- create a new global options file data/GameOptions.xml for all global
options.
- create new game-specific option files data/<game>/Options.xml.  Global
options can be overridden here, or even invalidated (e.g. 'use="no" ').
- add an 'undefined' attribute, per Stefan's suggestion.
- parse these files from both the GameSetupWindow and Game classes.

Erik.

> -----Original Message-----
> From: Stefan Frey [mailto:ste...@we...]
> Sent: Friday, October 28, 2011 10:37 AM
> To: Development list for Rails: an 18xx game
> Subject: Re: [Rails-devel] 18EU game option: unlimited plain track
> 
> Bill & Erik:
> just a short comment on the implementation:
> 
> As you know all options are duplicated in both the central GamesList.xml
as in
> the game-specific Game.xml.
> 
> However the default attribute of the GameOption element in Game.xml has
> a different effect for Rails than the default attribute for the Option
element
> in GamesList.xml.
> 
> A) Default of Option in GamesList.xml
> This is the default value suggested to use if a new game gets started.
> A saved game always saves the concrete setting of each option regardless
if
> this is the default or not.
> This value will never effect loaded games.
> 
> B) Default of GameOption in Game.xml:
> This is default value is ONLY used for loaded games that do not have the
> value defined as the option was previously unimplemented for that specific
> game.
> So a better name for this attribute would be undefined. Even better would
> be merging the two option elements and keep default and undefined
> attributes aside.
> 
> A rule of thumb if one introduces new values is simply setting the default
in
> GamesList.xml to the value best suited for that game and the default in
> Game.xml to that value that existing games had been used implicitly.
> 
> As both games with a changed option (1826 and 1851) had that option
> defined before it does not matter, as the save files will keep their
selected
> option and will not change without players being aware.
> 
> Stefan
> 
> 
> On Thursday, October 27, 2011 10:28:40 am Erik Vos wrote:
> > Bill,
> >
> > Thanks. I have applied your update.
> > For 1826 and 1851 I have set the default value to "Yellow Plain". For
> > 1851 it's in the rules, and for 1826 (v1) in the (as I understand:
> > "official") Steve Thomas/Chris Lawson clarification.
> > I haven't checked other games; the Rules Differences site does not
> > mention any other games that we currently cover in Rails.
> >
> > Apologies that I have not included your name as the Author of this and
> > the previous fix - I'm just now discovering that I can and should set
> > the correct Author while committing.
> > Hopefully I'll remember it next time...
> >
> > Erik.
> >
> > > -----Original Message-----
> > > From: Bill Rosgen [mailto:ro...@gm...]
> > > Sent: Thursday, October 27, 2011 9:21 AM
> > > To: Development list for Rails: an 18xx game
> > > Subject: Re: [Rails-devel] 18EU game option: unlimited plain track
> > >
> > > Erik,
> > >
> > > I've attached patches that should enable the option for all games
> > > that had unlimited track as an option, as well as for 1889, which
> > > did not for
> >
> > reasons I
> >
> > > do not understand.  (I left it out of only the few prototype games
> > > that
> >
> > have
> >
> > > no game options.)
> > >
> > > I've also renamed the option to "Yellow Plain".
> > >
> > > I can find no quote from the designer as to whether or not he
> > > prefers unlimited plain yellow track in 18EU.  I've left the default
> > > option as
> >
> > 'No' in all
> >
> > > cases, though it is reasonable to change this for 1826 and 1851.
> > > The
> > > 1851 rules I can find on the internet suggest that the number of
> > > 7,8,9 tiles provided is not intended to be a limit.  My internet
> > > connection is
> >
> > currently
> >
> > > quite poor, and so I am unable to verify that this is the rule also
> > > in
> >
> > 1826.  (The
> >
> > > 18xx difference list states that plain yellow track is unlimited in
> > > both
> >
> > of these
> >
> > > games.)
> > >
> > > As usual, there are two patches, the first in git format and the
> > > second in
> >
> > Egit
> >
> > > format.
> > >
> > > Bill
> >
> > ----------------------------------------------------------------------
> > -----
> > --- The demand for IT networking professionals continues to grow, and
> > the demand for specialized networking skills is growing even more
rapidly.
> > Take a complimentary Learning@Cisco Self-Assessment and learn about
> > Cisco certifications, training, and career opportunities.
> > http://p.sf.net/sfu/cisco-dev2dev
> > _______________________________________________
> > Rails-devel mailing list
> > Rai...@li...
> > https://lists.sourceforge.net/lists/listinfo/rails-devel
> 
>
----------------------------------------------------------------------------
--
> The demand for IT networking professionals continues to grow, and the
> demand for specialized networking skills is growing even more rapidly.
> Take a complimentary Learning@Cisco Self-Assessment and learn about
> Cisco certifications, training, and career opportunities.
> http://p.sf.net/sfu/cisco-dev2dev
> _______________________________________________
> Rails-devel mailing list
> Rai...@li...
> https://lists.sourceforge.net/lists/listinfo/rails-devel

[Rails-devel] 1825 half-tiles

[Stefan F. <ste...@we...>]

Actually I found this mail sitting in my draft folder.
It intended to provide half hexes for 1825. 
I do not know if this is still required, I lost track on the progress of 1825 
lately (if there has been any).
Stefan


Some time ago I edited the SVG files of the empty hex to create the half hex, 
but forgot to send them out. I know that the current support of 1825 already 
allows to lay track off the map, but there is no visual hint, where this is 
possible. So I wonder if they could be added. 
My experience now that for small changes it is actually much easier to edit 
the SVG directly than using Inkscape (the edit took hardly more time than 
writing this mail)

Re: [Rails-devel] 18EU game option: unlimited plain track

[Stefan F. <ste...@we...>]

Bill & Erik:
just a short comment on the implementation:

As you know all options are duplicated in both the central GamesList.xml as in 
the game-specific Game.xml. 

However the default attribute of the GameOption element in Game.xml has a 
different effect for Rails than the default attribute for the Option element 
in GamesList.xml.

A) Default of Option in GamesList.xml
This is the default value suggested to use if a new game gets started.
A saved game always saves the concrete setting of each option regardless if 
this is the default or not.
This value will never effect loaded games.

B) Default of GameOption in Game.xml:
This is default value is ONLY used for loaded games that do not have the value
defined as the option was previously unimplemented for that specific game.
So a better name for this attribute would be undefined. Even better would be 
merging the two option elements and keep default and undefined attributes 
aside.

A rule of thumb if one introduces new values is simply setting the default in 
GamesList.xml to the value best suited for that game and the default in 
Game.xml to that value that existing games had been used implicitly. 

As both games with a changed option (1826 and 1851) had that option defined 
before it does not matter, as the save files will keep their selected option 
and will not change without players being aware.

Stefan


On Thursday, October 27, 2011 10:28:40 am Erik Vos wrote:
> Bill,
> 
> Thanks. I have applied your update.
> For 1826 and 1851 I have set the default value to "Yellow Plain". For 1851
> it's in the rules, and for 1826 (v1) in the (as I understand: "official")
> Steve Thomas/Chris Lawson clarification.
> I haven't checked other games; the Rules Differences site does not mention
> any other games that we currently cover in Rails.
> 
> Apologies that I have not included your name as the Author of this and the
> previous fix - I'm just now discovering that I can and should set the
> correct Author while committing.
> Hopefully I'll remember it next time...
> 
> Erik.
> 
> > -----Original Message-----
> > From: Bill Rosgen [mailto:ro...@gm...]
> > Sent: Thursday, October 27, 2011 9:21 AM
> > To: Development list for Rails: an 18xx game
> > Subject: Re: [Rails-devel] 18EU game option: unlimited plain track
> > 
> > Erik,
> > 
> > I've attached patches that should enable the option for all games that
> > had unlimited track as an option, as well as for 1889, which did not for
> 
> reasons I
> 
> > do not understand.  (I left it out of only the few prototype games that
> 
> have
> 
> > no game options.)
> > 
> > I've also renamed the option to "Yellow Plain".
> > 
> > I can find no quote from the designer as to whether or not he prefers
> > unlimited plain yellow track in 18EU.  I've left the default option as
> 
> 'No' in all
> 
> > cases, though it is reasonable to change this for 1826 and 1851.  The
> > 1851 rules I can find on the internet suggest that the number of 7,8,9
> > tiles provided is not intended to be a limit.  My internet connection is
> 
> currently
> 
> > quite poor, and so I am unable to verify that this is the rule also in
> 
> 1826.  (The
> 
> > 18xx difference list states that plain yellow track is unlimited in both
> 
> of these
> 
> > games.)
> > 
> > As usual, there are two patches, the first in git format and the second
> > in
> 
> Egit
> 
> > format.
> > 
> > Bill
> 
> ---------------------------------------------------------------------------
> --- The demand for IT networking professionals continues to grow, and the
> demand for specialized networking skills is growing even more rapidly.
> Take a complimentary Learning@Cisco Self-Assessment and learn
> about Cisco certifications, training, and career opportunities.
> http://p.sf.net/sfu/cisco-dev2dev
> _______________________________________________
> Rails-devel mailing list
> Rai...@li...
> https://lists.sourceforge.net/lists/listinfo/rails-devel

[Rails-devel] Fwd: [18xx] Plain track in 18EU

[Chris S. <chr...@gm...>]

FYI

--
Chris

Please consider the environment before printing this e-mail.


---------- Forwarded message ----------
From: David Hecht <Ba...@ea...>
Date: Thu, Oct 27, 2011 at 6:26 AM
Subject: Re: [18xx] Plain track in 18EU
To: 18...@ya...


**


The most exact reply that I can give is that I worked diligently
throughout the development to see to it that there would be no track
shortages of any kind. But--in a formal sense--the answer is no:
however, no one--including me--would take exception if you played as if
it were.


On 10/27/2011 9:03 AM, Chris Shaffer wrote:
> Is plain yellow track in 18EU unlimited?
>
> --
> Chris
>
> Please consider the environment before printing this e-mail.
>
>
> [Non-text portions of this message have been removed]
>
>
>
> ------------------------------------
>
> This is a message from the 18xx mailing list.Yahoo! Groups Links
>
>
>
>

 __._,_.___
  Reply to sender<ba...@ea...?subject=Re%3A%20%5B18xx%5D%20Plain%20track%20in%2018EU>|
Reply
to group<18...@ya...?subject=Re%3A%20%5B18xx%5D%20Plain%20track%20in%2018EU>|
Reply
via web post<http://groups.yahoo.com/group/18xx/post;_ylc=X3oDMTJwZTF1bTBzBF9TAzk3MzU5NzE0BGdycElkAzExOTgyOQRncnBzcElkAzE3MDUwNTI4OTYEbXNnSWQDMzM5MDYEc2VjA2Z0cgRzbGsDcnBseQRzdGltZQMxMzE5NzIxOTgy?act=reply&messageNum=33906>|
Start
a New Topic<http://groups.yahoo.com/group/18xx/post;_ylc=X3oDMTJkMDZsOGsxBF9TAzk3MzU5NzE0BGdycElkAzExOTgyOQRncnBzcElkAzE3MDUwNTI4OTYEc2VjA2Z0cgRzbGsDbnRwYwRzdGltZQMxMzE5NzIxOTgy>
Messages in this
topic<http://groups.yahoo.com/group/18xx/message/33905;_ylc=X3oDMTM1M2NsYXI2BF9TAzk3MzU5NzE0BGdycElkAzExOTgyOQRncnBzcElkAzE3MDUwNTI4OTYEbXNnSWQDMzM5MDYEc2VjA2Z0cgRzbGsDdnRwYwRzdGltZQMxMzE5NzIxOTgyBHRwY0lkAzMzOTA1>(
2)
 Recent Activity:

   - New Members<http://groups.yahoo.com/group/18xx/members;_ylc=X3oDMTJlcjBiYjRkBF9TAzk3MzU5NzE0BGdycElkAzExOTgyOQRncnBzcElkAzE3MDUwNTI4OTYEc2VjA3Z0bARzbGsDdm1icnMEc3RpbWUDMTMxOTcyMTk4Mg--?o=6>
   1

 Visit Your Group<http://groups.yahoo.com/group/18xx;_ylc=X3oDMTJkODNubnFiBF9TAzk3MzU5NzE0BGdycElkAzExOTgyOQRncnBzcElkAzE3MDUwNTI4OTYEc2VjA3Z0bARzbGsDdmdocARzdGltZQMxMzE5NzIxOTgy>
 This is a message from the 18xx mailing list.
 MARKETPLACE

Stay on top of your group activity without leaving the page you're on - Get
the Yahoo! Toolbar
now.<http://global.ard.yahoo.com/SIG=15or2hr8e/M=493064.14543979.14562481.13298430/D=groups/S=1705052896:MKP1/Y=YAHOO/EXP=1319729182/L=433e99c6-009f-11e1-b86b-7364ee0e6508/B=KNu0F9j8fbg-/J=1319721982572564/K=rb_fiboBWG9qmz46OBoJ7g/A=6060255/R=0/SIG=1194m4keh/*http://us.toolbar.yahoo.com/?.cpdl=grpj>
   [image: Yahoo!
Groups]<http://groups.yahoo.com/;_ylc=X3oDMTJjNGkzMzBkBF9TAzk3MzU5NzE0BGdycElkAzExOTgyOQRncnBzcElkAzE3MDUwNTI4OTYEc2VjA2Z0cgRzbGsDZ2ZwBHN0aW1lAzEzMTk3MjE5ODI->
Switch to: Text-Only<18x...@ya...?subject=Change+Delivery+Format:+Traditional>,
Daily Digest <18x...@ya...?subject=Email+Delivery:+Digest> •
Unsubscribe <18x...@ya...?subject=Unsubscribe> • Terms
of Use <http://docs.yahoo.com/info/terms/>
   .

__,_._,___

Re: [Rails-devel] 18EU game option: unlimited plain track

[John A. T. <ja...@ja...>]

For the games I publish, here are the ones which definitively state whether
7/8/9 are unlimited or not:

   - 1812 - unlimited [7.3.2,p7]
   - 1846 - unlimited [6.22, p5]
   - 1889 - not unlimited [the beginner variant specifically adds extra
   7/8/9, p12]
   - 18Ardennes - unlimited [6.3, p8]
   - 18West - unlimited [8.1, p12]

The rest do not specify one way or the other.

-- 
John A. Tamplin

Re: [Rails-devel] 18EU game option: unlimited plain track

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

Bill,

Thanks. I have applied your update.  
For 1826 and 1851 I have set the default value to "Yellow Plain". For 1851
it's in the rules, and for 1826 (v1) in the (as I understand: "official")
Steve Thomas/Chris Lawson clarification.
I haven't checked other games; the Rules Differences site does not mention
any other games that we currently cover in Rails.

Apologies that I have not included your name as the Author of this and the
previous fix - I'm just now discovering that I can and should set the
correct Author while committing.
Hopefully I'll remember it next time...

Erik.

> -----Original Message-----
> From: Bill Rosgen [mailto:ro...@gm...]
> Sent: Thursday, October 27, 2011 9:21 AM
> To: Development list for Rails: an 18xx game
> Subject: Re: [Rails-devel] 18EU game option: unlimited plain track
> 
> Erik,
> 
> I've attached patches that should enable the option for all games that had
> unlimited track as an option, as well as for 1889, which did not for
reasons I
> do not understand.  (I left it out of only the few prototype games that
have
> no game options.)
> 
> I've also renamed the option to "Yellow Plain".
> 
> I can find no quote from the designer as to whether or not he prefers
> unlimited plain yellow track in 18EU.  I've left the default option as
'No' in all
> cases, though it is reasonable to change this for 1826 and 1851.  The 1851
> rules I can find on the internet suggest that the number of 7,8,9 tiles
> provided is not intended to be a limit.  My internet connection is
currently
> quite poor, and so I am unable to verify that this is the rule also in
1826.  (The
> 18xx difference list states that plain yellow track is unlimited in both
of these
> games.)
> 
> As usual, there are two patches, the first in git format and the second in
Egit
> format.
> 
> Bill

Re: [Rails-devel] 18EU game option: unlimited plain track

[Bill R. <ro...@gm...>]

Erik,

I've attached patches that should enable the option for all games that had unlimited track as an option, as well as for 1889, which did not for reasons I do not understand.  (I left it out of only the few prototype games that have no game options.)

I've also renamed the option to "Yellow Plain".

I can find no quote from the designer as to whether or not he prefers unlimited plain yellow track in 18EU.  I've left the default option as 'No' in all cases, though it is reasonable to change this for 1826 and 1851.  The 1851 rules I can find on the internet suggest that the number of 7,8,9 tiles provided is not intended to be a limit.  My internet connection is currently quite poor, and so I am unable to verify that this is the rule also in 1826.  (The 18xx difference list states that plain yellow track is unlimited in both of these games.)

As usual, there are two patches, the first in git format and the second in Egit format.

Bill

Re: [Rails-devel] 18EU game option: unlimited plain track

[John D. G. <jd...@di...>]

On 2011-10-25 03:38, Bill Rosgen wrote:
> I've attached a couple of patches, again the first is in git format and the second is in Egit format.  If this seems like a good thing to apply globally, let me know and I will produce a similar patch that applies to all of the games implemented in Rails.

I would like it to be global.  1853 v1 gives this as an optional rule, and I've seen
it in other games, including as a house rule.

Re: [Rails-devel] 18EU game option: unlimited plain track

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

My comments:

1. The 18EU rules don't specify unlimited yellow plain track tiles, so this
report isn't about a bug at all (which I guess explains why I have ignored
it so far).  Indeed several games do specify this feature, and it's perhaps
not a bad idea to open it up to all games.  BTW, has any word from the
designer been heard that he wants it this way for 18EU?

2. I suppose your layout-based behind-the-scenes selection of #7, #8 and #9
will do the job.  I just want to remark that in fact it hardcodes these
tiles even more that an explicit list (or some tile-specific  XML attribute)
would have done.  

3. IMO, the intermediate option should be named "Yellow Plain", not just
"Plain".  Or perhaps "Some" or "Partial" to leave open the option of
including (a list of) other tiles.

Erik.

> -----Original Message-----
> From: Bill Rosgen [mailto:ro...@gm...]
> Sent: Tuesday, October 25, 2011 12:38 PM
> To: Development list for Rails: an 18xx game
> Subject: [Rails-devel] 18EU game option: unlimited plain track
> 
> Bug 3064825 requests the ability to select unlimited plain track only
(i.e. tiles
> 7,8,9).  It is reported that this is included in the 18EU rules, though I
cannot
> find it in my copy.  In any case, it maybe doesn't hurt to have the
option.
> 
> I've attached a patch that makes this change for 18EU (and shouldn't break
> any other games).  The unlimited tiles checkbox is expanded to take the
> values 'No,Plain,Yes', with the default remaining 'No'.  I have also had
to
> make a change to Tile.java to implement the 'Plain' option.  Any tile with
no
> stations and exactly one piece of track is considered 'Plain'.  In 18EU
this
> applies to exactly tiles 7,8, and 9, but I would rather not hardcode these
tile
> ids.  I've also added the option to the 1826 prototype data files, but
it's not
> currently available as no variants are defined in GameList.xml.
> 
> It is maybe worth adding this test as a function isPlain() in the Tile
class, but
> I'm not sure: this makes the test easier to find, but will any other code
will
> ever need to ask if a tile is 'Plain'?
> 
> Other than the comment on the bug that this is in the rules for 18EU and
> 1826, I see no reason to limit this to 18EU.  If this is thought to be a
good idea,
> I can easily make changes to the other data files to enable the option
across
> all games.
> 
> I've attached a couple of patches, again the first is in git format and
the
> second is in Egit format.  If this seems like a good thing to apply
globally, let
> me know and I will produce a similar patch that applies to all of the
games
> implemented in Rails.
> 
> 
> Bill

Re: [Rails-devel] 18EU game option: unlimited plain track

[John A. T. <ja...@ja...>]

On Tue, Oct 25, 2011 at 7:11 AM, Phil Davies <de...@gm...> wrote:

> If I recall 1851 is supposed to be unlimited plain track
> too...although that might already be included in rails as it stands


Most DH games specifically say that plain track (7/8/9) are unlimited.

-- 
John A. Tamplin

Re: [Rails-devel] 18GA map: cost of hex J10

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

Thanks, Bill.  I have applied this fix.

Erik.

> -----Original Message-----
> From: Bill Rosgen [mailto:ro...@gm...]
> Sent: Tuesday, October 25, 2011 12:26 PM
> To: Development list for Rails: an 18xx game
> Subject: [Rails-devel] 18GA map: cost of hex J10
> 
> Bug 3426993 reports that in Rails hex J10 is missing it's cost ($40).  All
of the
> maps I can find online show this cost, and so I assume this is just an
oversight
> in the data files.  The attached patch adds the cost.
> 
> The first patch is in git format, and the second is in Egit format.  Both
patches
> should be identical.  Of course, the fix is only a few characters, so it
may be
> easier to fix it by hand than to apply the patch.
> 
> Bill

Re: [Rails-devel] 18EU game option: unlimited plain track

[Phil D. <de...@gm...>]

If I recall 1851 is supposed to be unlimited plain track
too...although that might already be included in rails as it stands

On 25 October 2011 11:38, Bill Rosgen <ro...@gm...> wrote:
> Bug 3064825 requests the ability to select unlimited plain track only (i.e. tiles 7,8,9).  It is reported that this is included in the 18EU rules, though I cannot find it in my copy.  In any case, it maybe doesn't hurt to have the option.
>
> I've attached a patch that makes this change for 18EU (and shouldn't break any other games).  The unlimited tiles checkbox is expanded to take the values 'No,Plain,Yes', with the default remaining 'No'.  I have also had to make a change to Tile.java to implement the 'Plain' option.  Any tile with no stations and exactly one piece of track is considered 'Plain'.  In 18EU this applies to exactly tiles 7,8, and 9, but I would rather not hardcode these tile ids.  I've also added the option to the 1826 prototype data files, but it's not currently available as no variants are defined in GameList.xml.
>
> It is maybe worth adding this test as a function isPlain() in the Tile class, but I'm not sure: this makes the test easier to find, but will any other code will ever need to ask if a tile is 'Plain'?
>
> Other than the comment on the bug that this is in the rules for 18EU and 1826, I see no reason to limit this to 18EU.  If this is thought to be a good idea, I can easily make changes to the other data files to enable the option across all games.
>
> I've attached a couple of patches, again the first is in git format and the second is in Egit format.  If this seems like a good thing to apply globally, let me know and I will produce a similar patch that applies to all of the games implemented in Rails.
>
> Bill
>
>
> ------------------------------------------------------------------------------
> The demand for IT networking professionals continues to grow, and the
> demand for specialized networking skills is growing even more rapidly.
> Take a complimentary Learning@Cisco Self-Assessment and learn
> about Cisco certifications, training, and career opportunities.
> http://p.sf.net/sfu/cisco-dev2dev
> _______________________________________________
> Rails-devel mailing list
> Rai...@li...
> https://lists.sourceforge.net/lists/listinfo/rails-devel
>
>

[Rails-devel] 18EU game option: unlimited plain track

[Bill R. <ro...@gm...>]

Bug 3064825 requests the ability to select unlimited plain track only (i.e. tiles 7,8,9).  It is reported that this is included in the 18EU rules, though I cannot find it in my copy.  In any case, it maybe doesn't hurt to have the option.

I've attached a patch that makes this change for 18EU (and shouldn't break any other games).  The unlimited tiles checkbox is expanded to take the values 'No,Plain,Yes', with the default remaining 'No'.  I have also had to make a change to Tile.java to implement the 'Plain' option.  Any tile with no stations and exactly one piece of track is considered 'Plain'.  In 18EU this applies to exactly tiles 7,8, and 9, but I would rather not hardcode these tile ids.  I've also added the option to the 1826 prototype data files, but it's not currently available as no variants are defined in GameList.xml.

It is maybe worth adding this test as a function isPlain() in the Tile class, but I'm not sure: this makes the test easier to find, but will any other code will ever need to ask if a tile is 'Plain'?

Other than the comment on the bug that this is in the rules for 18EU and 1826, I see no reason to limit this to 18EU.  If this is thought to be a good idea, I can easily make changes to the other data files to enable the option across all games.

I've attached a couple of patches, again the first is in git format and the second is in Egit format.  If this seems like a good thing to apply globally, let me know and I will produce a similar patch that applies to all of the games implemented in Rails.

Bill

[Rails-devel] 18GA map: cost of hex J10

[Bill R. <ro...@gm...>]

Bug 3426993 reports that in Rails hex J10 is missing it's cost ($40).  All of the maps I can find online show this cost, and so I assume this is just an oversight in the data files.  The attached patch adds the cost.

The first patch is in git format, and the second is in Egit format.  Both patches should be identical.  Of course, the fix is only a few characters, so it may be easier to fix it by hand than to apply the patch.

Bill

Re: [Rails-devel] 18GA: Movement from L3 to M3

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

Thanks for reporting. Probably a typo.  I have issued a fix.  

Erik.

> -----Original Message-----
> From: Rick Westerman [mailto:wes...@pu...]
> Sent: Monday, October 24, 2011 7:29 PM
> To: Development List Rails
> Subject: [Rails-devel] 18GA: Movement from L3 to M3
> 
> In reference to the below, I looked at the physical game and M3 there has
a
> value of '190'.  Thus it appears to be wrong in the Rails version.
> 
> --------
> Just noticed in an ongoing 18GA game that tokens went from stock price L3
> to M3.  M3, at least on the Rails version, has only a default value of
"100".  I
> have not checked my physical copy to make sure e if M3 should exist.
> --------
> --
> Rick Westerman
> wes...@pu...
> 
>
----------------------------------------------------------------------------
--
> The demand for IT networking professionals continues to grow, and the
> demand for specialized networking skills is growing even more rapidly.
> Take a complimentary Learning@Cisco Self-Assessment and learn about
> Cisco certifications, training, and career opportunities.
> http://p.sf.net/sfu/cisco-dev2dev
> _______________________________________________
> Rails-devel mailing list
> Rai...@li...
> https://lists.sourceforge.net/lists/listinfo/rails-devel

[Rails-devel] 18GA: Movement from L3 to M3

[Rick W. <wes...@pu...>]

In reference to the below, I looked at the physical game and M3 there has a value of '190'.  Thus it appears to be wrong in the Rails version.

--------
Just noticed in an ongoing 18GA game that tokens went from stock price L3 to M3.  M3, at least on the Rails version, has only a default value of "100".  I have not checked my physical copy to make sure e if M3 should exist.
--------
-- 
Rick Westerman 
wes...@pu...

[Rails-devel] 18GA: Movement from L3 to M3

[Rick W. <wes...@pu...>]

Just noticed in an ongoing 18GA game that tokens went from stock price L3 to M3.  M3, at least on the Rails version, has only a default value of "100".  I have not checked my physical copy to make sure e if M3 should exist.

-- 
Rick Westerman 
wes...@pu...

Re: [Rails-devel] Test report: 1835 in Rails 1.5.1

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

> A perfect solution would merge all those checks into one. However this is
not
> so easy as it might seem in first place. On a second look it is a
non-trivial task
> to find out if and where are valid tile lays considering all constraints
> (operating company network, operating company funding, tile upgrade
> charts, tile availability, local neighborhood restrictions for tile
upgrades,
> checking for the permissive or (semi-)restrictive upgrade rules etc.).

I think the main impediment is that the game engine is not yet aware of the
valid routes of the operating company (for tile laying purposes). The
LayTile action objects are already prepared to carry a list of hexes where a
tile can be laid, but the game engine is not yet able to compose such a
list.

Erik.

Re: [Rails-devel] Test report: 1835 in Rails 1.5.1

[John D. G. <jd...@di...>]

On 2011-10-19 09:36, Stefan Frey wrote:
> This is a  follow-up to the one of the issues in the 1835 test report:
> 
> I think we should highlight somewhere in the wiki and the comments for the 
> restrictions that the tile and token laying rule enforcement and highlighting 
> currently suggest and allows some illegal tile and token lays. However both 
> mechanisms should NEVER disallow or forget to suggest allowed and illegal tile 
> lays. The latter are always bugs and should be reported. The other round is 
> currently unavoidable and have to be handled by the players themselves.
> 
> I quickly went through the 1835 game file and I have not found a situation 
> where the tile/token highlighting forgot to suggest a valid hex, but it is 
> easy to make a mistake here.
> 
> So if John or Erik could possible point out some cases the algorithm missed 
> upgradable or buildable hexes in that test game, that would be helpful.

As best I recall, when the program suggested any builds at all, it suggested
all the legal build locations.

But there were cases where NO hexes were highlighted for building, and some
builds were still possible.  Example: M6 has built a loop from NW Hamburg to
Kiel to NE Hamburg, so it can legally build a "dit" out of Schwerin but no
hexes are highlighted.  (The program still allowed the build, however.)

The opposite case was more common: when M1 is building, (unbuilt) Koln and
Essen are highlighted even though M1 doesn't have $50 in treasury.