URL:
  <http://gna.org/bugs/?20054>

                 Summary: Rivers as terrain in supplied tilesets?
                 Project: Freeciv
            Submitted by: jtn
            Submitted on: Sat Aug 11 20:11:38 2012
                Category: art
                Severity: 3 - Normal
                Priority: 5 - Normal
                  Status: Need Info
             Assigned to: None
        Originator Email: 
             Open/Closed: Open
                 Release: 
         Discussion Lock: Any
        Operating System: None
         Planned Release: 

    _______________________________________________________

Details:

freim (Hogne) on IRC was asking why our tilesets have both "river-as-special"
and "river-as-terrain" definitions, and whether new tilesets need both.

For instance, Amplio2 has the following river-related stuff:


data/amplio2/terrain1.spec:
 2,  0, "t.l0.grassland1"
 2,  0, "t.l0.t_river1"
...
 11, 4, "ts.grassland_resources", "ts.river_resources"

data/amplio2/water.spec:
; Rivers (as special type), and whether north, south, east, west 
; also has river or is ocean:

 2,  0, "tx.s_river_n0e0s0w0"
 2,  1, "tx.s_river_n0e0s0w1"
 2,  2, "tx.s_river_n0e0s1w0"
 2,  3, "tx.s_river_n0e0s1w1"
 2,  4, "tx.s_river_n0e1s0w0"
 2,  5, "tx.s_river_n0e1s0w1"
 2,  6, "tx.s_river_n0e1s1w0"
 2,  7, "tx.s_river_n0e1s1w1"
 3,  0, "tx.s_river_n1e0s0w0"
 3,  1, "tx.s_river_n1e0s0w1"
 3,  2, "tx.s_river_n1e0s1w0"
 3,  3, "tx.s_river_n1e0s1w1"
 3,  4, "tx.s_river_n1e1s0w0"
 3,  5, "tx.s_river_n1e1s0w1"
 3,  6, "tx.s_river_n1e1s1w0"
 3,  7, "tx.s_river_n1e1s1w1"

; Rivers as overlay

 2,  0, "t.t_river_n0e0s0w0"
 2,  1, "t.t_river_n0e0s0w1"
 2,  2, "t.t_river_n0e0s1w0"
 2,  3, "t.t_river_n0e0s1w1"
 2,  4, "t.t_river_n0e1s0w0"
 2,  5, "t.t_river_n0e1s0w1"
 2,  6, "t.t_river_n0e1s1w0"
 2,  7, "t.t_river_n0e1s1w1"
 3,  0, "t.t_river_n1e0s0w0"
 3,  1, "t.t_river_n1e0s0w1"
 3,  2, "t.t_river_n1e0s1w0"
 3,  3, "t.t_river_n1e0s1w1"
 3,  4, "t.t_river_n1e1s0w0"
 3,  5, "t.t_river_n1e1s0w1"
 3,  6, "t.t_river_n1e1s1w0"
 3,  7, "t.t_river_n1e1s1w1"

;river outlets

 4,  0, "tx.river_outlet_n"
 4,  1, "tx.river_outlet_e"
 4,  2, "tx.river_outlet_s"
 4,  3, "tx.river_outlet_w"


I find the tileset code hard to follow, but with our default ruleset, as far
as I can tell, only s_river_* and tx_river_outlet_* are read (experimentally
this is the case). I can't see code that would read any of the rest, absent a
terrain type called "river".

Does anyone remember why the others are there? Are they some ancient backward
compatibility thing that can now go? Or is there some modpack out there that
treats river as a terrain type, or something? Can anyone remember the
history?

Given the lack of documentation, it would make tileset authors' life easier if
extraneous fluff could be omitted from the examples we provide.




    _______________________________________________________

Reply to this item at:

  <http://gna.org/bugs/?20054>

_______________________________________________
  Message sent via/by Gna!
  http://gna.org/


_______________________________________________
Freeciv-dev mailing list
Freeciv-dev@gna.org
https://mail.gna.org/listinfo/freeciv-dev

Reply via email to