MegaGlest Forum

MegaGlest => Bug reports => Closed bug reports => Topic started by: Baŝto on 22 August 2013, 21:47:05

Title: [fixed] 3.8.0 beta1,list-scerarios and load-scenario incompatible
Post by: Baŝto on 22 August 2013, 21:47:05
 64bit archlinux:

Code: [Select]
megaglest --list-scenarios and
Code: [Select]
megaglest --load-scenario= are not compatible.

Code: [Select]
megaglest --list-scenarios lists the folder names of all scenarios

Code: [Select]
megaglest --load-scenario= expects the scenario name how it is defined in the .lng-file



Edit (tomreyn): Removed [bug] tag, not needed on the bug reports forum.
Title: Re: [bug] 3.8.0 beta1, 64bit archlinux: list-scerarios and load-scenario incompatibl
Post by: Omega on 23 August 2013, 02:00:52
I'm not quite sure I understand. The name of the scenario is decided entirely by the folder. The language file has no say over the scenario name as far as I know. The scenario's XML file must be named <folderName>.xml and the language files must be named <folderName>_<language>.lng.

For example, running megaglest --list-scenarios on the latest stable release produces (EDIT: except the benchmark scenario isn't part of the release):

Code: [Select]
Scenarios found:
===========================================
amazones
amazones_light
anarchy
beehive_castle
beginner_1
beginner_2
beginner_3
benchmark
capture_enemy_flag
duel
egypt_mayhem
indian_attack
kill_the_magic
magic_can_do_it
my_island
norsemen_attack
one_hope
siege_of_despair
storming
tech_and_magic
tough_duel
waterworld
===========================================
Total: 22

I can run, say, Egypt Mayhem with megaglest --load-scenario=egypt_mayhem, which works fine (despite the fact that in-game, the translator replaces underscores with spaces and Capitalizes The First Word Of Everything). The same works for scenarios with an actual language file, like storming.

If this wasn't a misunderstanding of the commands, can you please give a specific example of how the features are incompatible?
Title: Re: 3.8.0 beta1, 64bit archlinux: list-scerarios and load-scenario incompatible
Post by: Baŝto on 23 August 2013, 18:08:25
First of all: I use the German localization.

Code: [Select]
megaglest --load-scenario=egypt_mayhem works, that’s right, this scenario name does not seem being translated. And just few scenario names are translated, at least in the German version.

I can’t run
Code: [Select]
megaglest --load-scenario=amazones instead I have to use
Code: [Select]
megaglest --load-scenario=amazonen
Title: Re: 3.8.0 beta1, 64bit archlinux: list-scerarios and load-scenario incompatible
Post by: filux on 23 August 2013, 18:35:51
wrong thinking

everything in console, inside a files, etc. is default in english and should be always in english
Title: Re: 3.8.0 beta1, 64bit archlinux: list-scerarios and load-scenario incompatible
Post by: Baŝto on 23 August 2013, 23:45:31
wrong thinking

everything in console, inside a files, etc. is default in english and should be always in english
I totally agree with that, but
Code: [Select]
--load-scenario= only works with the translated names … and that’s the problem
Title: Re: 3.8.0 beta1, 64bit archlinux: list-scerarios and load-scenario incompatible
Post by: Omega on 24 August 2013, 00:06:05
I agree that this should be considered a bug. The two commands should be 100% compatible. Ideally, we'd be able to use both the translated name and the folder name (which isn't necessarily English, by the way), but that would raise the issue of conflicts. Best to just use the folder name when launching scenarios from the command line.
Title: Re: 3.8.0 beta1, 64bit archlinux: list-scerarios and load-scenario incompatible
Post by: titi on 25 August 2013, 20:25:54
Yes, I also think thats a bug.  Regarding these command line params, even the english translation is wrong. There should be used the filenames instead .
Same for translated unit names in logfiles and so on. A translation should only be shown in the GUI, that's all.
Title: Re: 3.8.0 beta1,list-scerarios and load-scenario incompatible
Post by: softcoder on 19 September 2013, 06:57:07
Fixed in svn rev#: 4550