UFO:Alien Invasion
General => Discussion => Topic started by: Rodmar on November 22, 2016, 12:02:59 am
-
Hello,
Before I post a bug report, I'd like to know if the following text that is displayed in red on some crashed UFO maps (Gunship, at least) when a soldier comes too close to the engines, is correctly translated in other languages in version 2.6.
In v2.5, this string can't be found in the .po file.
"The green smoke waving around this damaged alien propulsion device looks suspecious. Maybe you should avoid getting to close there."
Btw, "suspecious" could be corrected.
-
Huh, what happens if a soldier comes too close anyway ? Is that a new feature ?
-
It's like an invisible fire field; you suffer from radiations circa 15-20 HP/square you walk (in Power Armour). Green fumes particle effects are associated with it, the same as those used to mark a location on the Fuel Deposit map, but you don't have to walk through them. I play on v2.5, and you sure have played such a crash-landed Gunship map, did you? However, the only way to read this sentence is to walk close enough to an engine (or a separated engine). If you use to win those maps ever before one of your soldiers comes close, it's no wonder you never notice it.
Anyway as it appears in English, I wanted to know whether the string lies in the map file or in the source code. And if it could be made translatable. I'd bet there's the same localization problem with the new mission objectives, but I don't play v2.6. I hope I can play the Fuel Deposit map soon again.
Secondly, the Medikit section could be complemented so as to briefly mention that it can't treat radiation sickness effects on the spot, besides the use of painkillers.
-
It's better with a screenshot.
This soldier 's health will be reduced -15 HP per square (in the vicinity of the engine).
-
The string comes form the map itself (specifically base/maps/africa/af_craft_crash_gunboat.map) but it doesn't appear in the *.po files, probably our update scripts don't look in the *.map files for translatable text.
-
Thanks for the answer. Since you are aware of the "problem", there's no need for a report, I guess.
-
Perhaps posting a bug report would be nice for the record? Or later, if you notice some other problems of the same type?
-
Rather a feature request then, as a remainder.