Re: [Freeciv-Dev] [bug #18404] Option to continue playing after game end

23.07.2011 12:05, anonymous wrote: It would be nice if there would be a server-side option to continue playing after the game ends, for example if a surviving player wants to completely develop a map or deal with remaining enemies after a spaceship arrives or turns have elapsed. A similar option

[Freeciv-Dev] [bug #18404] Option to continue playing after game end

URL: Summary: Option to continue playing after game end Project: Freeciv Submitted by: None Submitted on: Sat 23 Jul 2011 06:05:34 AM UTC Category: freeciv.org Severity: 3 - No

[Freeciv-Dev] [bug #18396] Translations for help and options not displayed

Follow-up Comment #2, bug #18396 (project freeciv): Patches attached for settings bug. Help bug still a mystery. If it drags on, we should split it into a separate ticket. (file #13634, file #13635) ___ Additional Item Attachment: File na

[Freeciv-Dev] [patch #2784] Somaliland nation

Update of patch #2784 (project freeciv): Status: Ready For Test => Done Open/Closed:Open => Closed ___ Reply to this item at:

[Freeciv-Dev] [patch #2822] Barbadian nation

URL: Summary: Barbadian nation Project: Freeciv Submitted by: mixcoatl Submitted on: Fri 22 Jul 2011 11:16:23 PM GMT Category: rulesets Priority: 5 - Normal S

[Freeciv-Dev] [patch #2806] Improved Russian nation

Follow-up Comment #2, patch #2806 (project freeciv): > Question on order in city list: what are weights of population/age/historical importance? No particular order, I mostly maintained the order of the cities from the initial city list, and then added the capitals of all federal subjects, citie

[Freeciv-Dev] [bug #18397] Large City list randomly scrolls

Follow-up Comment #2, bug #18397 (project freeciv): Hm. Haven't dug out a 2.1.x to play with yet, but this sounds a *bit* like something that is finally addressed in 2.3.x, where various reports (including the city report) were redrawn at apparently-random times, losing their selections, etc. See

[Freeciv-Dev] [bug #18396] Translations for help and options not displayed

Update of bug #18396 (project freeciv): Planned Release: => 2.3.1,2.4.0 ___ Follow-up Comment #1: I can reproduce the options issues on Linux with the French localisation, and I'm got a pretty

[Freeciv-Dev] Freeciv 2.2.7 released

Freeciv 2.2.7 is now available for download. This release fixes a single serious bug in 2.2.6 which made changing government in the Gtk client difficult or impossible. See more details at . Source code and Windows packages are available from

[Freeciv-Dev] [bug #18397] Large City list randomly scrolls

Follow-up Comment #1, bug #18397 (project freeciv): Posted by Nutster. Sorry, I forgot to log in first. ___ Reply to this item at: ___ Message sent via/by Gna!

[Freeciv-Dev] [bug #18397] Large City list randomly scrolls

URL: Summary: Large City list randomly scrolls Project: Freeciv Submitted by: None Submitted on: Fri 22 Jul 2011 11:44:53 AM UTC Category: client-gtk-2.0 Severity: 2 - Minor

[Freeciv-Dev] [bug #18396] Translations for help and options not displayed

Additional Item Attachment, bug #18396 (project freeciv): File name: untranslated-geological.PNGSize:400 KB ___ Reply to this item at: ___ Message sent via

[Freeciv-Dev] [bug #18396] Translations for help and options not displayed

URL: Summary: Translations for help and options not displayed Project: Freeciv Submitted by: hubkow Submitted on: Fri 22 Jul 2011 01:35:42 PM CEST Category: client-gtk-2.0 Seve

[Freeciv-Dev] [bug #18394] self root_req'd techs are removed, even if a nation's init_tech lists it

Follow-up Comment #1, bug #18394 (project freeciv): I agree it did not work with v2.3.0-beta4 I did try to use LUA scripts to give such techs (root req itself) to a nation, but the tech does not appear in the tech tree, and it can not be used to enable other units or techs. However, I just inst

[Freeciv-Dev] [bug #18260] Trouble with menubars in Unity desktop environment (Ubuntu)

Follow-up Comment #4, bug #18260 (project freeciv): Attached a remastered patch for S2_2. (Note to self: just because git can move a patch cleanly between branches, doesn't mean that it can be applied without the history clues available to git...) (file #13625) __