URL:
<http://gna.org/patch/?6518>
Summary: foggedborders option(s) to always know own borders
Project: Freeciv
Submitted by: jtn
Submitted on: Sun 01 Nov 2015 13:09:19 UTC
Category: None
Priority: 5 - Normal
Status: Need Info
Privacy: Public
Assigned to: None
Originator Email:
Open/Closed: Open
Discussion Lock: Any
Planned Release: 2.6.0, 3.0.0
_______________________________________________________
Details:
As discussed in bug #17301, the current behaviour of foggedborders=TRUE that
tiles can be within your borders without this showing on your map is a bit
daft.
(See also bug #19917?)
Turn 'foggedborders' from a bool to an enumerated setting:
* DISABLED: all players always know all borders (current foggedborders=FALSE)
* FOREIGN: you always know where your own borders are, but don't see foreign
borders move unless you see the tile (new behaviour)
* ALL: you may have out of date info for even your own borders (current
foggedborders=TRUE)
Corner cases that need resolving with foggedborders=FOREIGN:
What do you see if someone steals your unseen tile -- unclaimed tile or
knowledge of claimer? I'm leaning toward the latter -- narratively, if you
heard that your distant frontier is no longer 'yours', you probably also heard
something about who took it. This may be the way you first learn of your
neighbours, which seems reasonable; and it means that if you know full well
who your neighbours are already, border gaps don't open up which the player
knows full well are not real.
(Don't know how hard this will be to implement.)
More controversial is what happens with diplomatic map transfer and shared
vision (between teammates and otherwise). From discussion in bug #17301:
>> [jtn] (And shared vision shares knowledge of borders.)
> [cazfi] You mean also those tiles that are not actually seen
> by the shared vision giver, but for which borders are known
> regardless? Why? I don't think there's even implementation
> cleanliness argument for this.
My belated answer:
Having no way to transfer knowledge of one's own borders without holes will be
annoying, just exporting the original problem to teammates and allies -- they
will end up with hole-y maps of your borders which they know full well aren't
correct, and could be unable to make correct decisions (e.g. routing around
your real borders if you're only at Peace and they can't go through).
Perhaps one-off map transfers and shared vision should be considered
separately?
* One-off transfers convey known-not-seen information and that could include
your current (then-correct) notion of your borders.
* Does shared vision include an implicit transfer of known-not-seen tiles, or
not? If not it needn't include your correct borders. If so, and the
known-not-seen information is transferred every turn, then IMO logically they
should get your updated borders.
If we have uses for both behaviours, the choice could be an extra value for
foggedborders, but I'd rather not have the additional complexity if we don't
need it.
Change of option format + intent to embed setting in supplied rulesets =>
consider for S2_6 d3f.
_______________________________________________________
Reply to this item at:
<http://gna.org/patch/?6518>
_______________________________________________
Message sent via/by Gna!
http://gna.org/
_______________________________________________
Freeciv-dev mailing list
[email protected]
https://mail.gna.org/listinfo/freeciv-dev
