The Battle for Wesnoth Forums

In the gameplay i found that i avoided certain unit types that seem suboptimal Totally. Figuring out the best units to recruit/recall is a huge part of this campaign, specially for players otherwise unfamiliar with Era of Magic, such as myself. Camel riders, Earth Elementals and Heavy Summoners see...

balance the campaign without calculating the possible gold from early finish bonus? Early finish bonus was introduced to Wesnoth only in 1.14, IIRC. To Lands Unknown is older than that. Some other popular campaigns also do without early finish bonus. Note that early finish bonus is a thorny matter....

[filter] only checks whether a unit is currently there, and has no relationship to the village ownership (in fact, it's possible a unit rests in village without capturing it.) A better alternative with store_locations is mentioned in the thread linked by Straff. And you may also check the Wiki: htt...

In response to this, I proposed "Freezing specific areas such as new/overhauled campaigns (such as WoF) early". The proposal of blocking string-heavy campaigns/reworks from being merged in some time window looks like good practice to implement. My response was regarding the first of Penta...

You should be using x,y in your StandardLocationFilter ( https://wiki.wesnoth.org/StandardLocationFilter ) instead. [store_locations] variable=sw_spots_current x=$sw_spots[$sw_turn].x y=$sw_spots[$sw_turn].y [/store_locations] find_in is meant for when you already got the output of another store_loc...

The en_US method needs that the deployers make sure to synchronize the original texts and the translated texts in every release, same as the current Wesnoth deployments. The en_US method introduced by IceSandslash seems to offer the option to avoid the potentially mistranslation only at build time....

But if a translator is going to translate the two new strings, then the translator will also have to translate the two modified strings too, because the old translations will probably not make much sense when combined with the new strings. The entire point is that if the 2 new strings aren't displa...

If the translation doesn't get fixed, then suddenly Delfador is going to be talking in a foreign language. Not a good UX. A newcomer getting butchered in Elensefar is also bad UX. The translation can be updated, though, and arguably it should be updated before being released, for the most complete ...

I disagree that adding new translatable strings to a stable release is "fine". Adding new translatable strings breaks all existing translations. There might be some cases where adding a new translatable string needs to be done in order to fix a critical bug, even in a stable release, but ...

a new #wenoth-tools domain (77 strings, 1 month of work) 1 month? What an overstatement. Some languages have already done it in literally negative time (as in the PR is still not merged). As the author of that PR, I can tell you and fellow forum lurkers that if you don't feel that your time is well...

To get a sense of the example I provided, the following screenshot is what POEdit would show for a fuzzy string. Note that the previous source text may be copied. https://i.imgur.com/mJTE3B0.png The following screenshot shows the translator adding a note that this string was last updated for the old...

I'm not sure what you mean when you say that the "canonical version of Wesnoth texts" will be in the en_US file, but then also that "Major changes regarding intention, personality, or whatever else the campaign author deems important would have to go into the campaign source, and the...

3. What, specifically, is meant by en_US here? At the moment of its creation, for each campaign/domain, it would be a file of the form: msgid "Same string in both lines." msgstr "Same string in both lines." After that, this file is to contain the canonical version of Wesnoth tex...

So for the original idea of having an en_US translation, the majority of translators who have replied have been against doing this, so at this point I don't think it's something we'll end up doing. In a similar way, some (most?) of the translators who have spoken up are also opposed to using pofix ...

Interesting ideas. I can only complement that games with economies based on 2+ types of resources generally use at least one of them as some sort of tech barrier. For example, wood in Warcraft 3 or gas in the Starcraft series limit how early and how many of the most powerful units you may produce. S...