Yes.Oberlus wrote: ↑Tue Dec 01, 2020 6:24 pmI take it as yes. From the strings I added myself, I can't remember of any that contained important information. I would remove all of them (I will be glad to do it once I get free time, maybe by the end of this year).Geoff the Medio wrote: ↑Tue Dec 01, 2020 5:00 pm Does that mean that of the strings that currently just contain "per population" can be removed from the stringtables?
RFC: A single source for default values (FOCS, python, stringtables, backend)
Moderator: Oberlus
Re: RFC: A single source for default values (FOCS, python, stringtables, backend)
Any code or patches in anything posted here is released under the CC and GPL licences in use for the FO project.
Look, ma... four combat bouts!
Look, ma... four combat bouts!
Re: RFC: A single source for default values (FOCS, python, stringtables, backend)
Ophiuchus, how is it going the ordeal with making named values work properly for all operating systems, providing consistent checksums with mutex here and there, and any other etcetera that I might be missing?
Re: RFC: A single source for default values (FOCS, python, stringtables, backend)
Thanks for your kind words. Should work on mac, win32 and linux to the best of my knowledge.
Any code or patches in anything posted here is released under the CC and GPL licences in use for the FO project.
Look, ma... four combat bouts!
Look, ma... four combat bouts!
Re: RFC: A single source for default values (FOCS, python, stringtables, backend)
Nah, I wont solve it. I simply implement some extra parsers for layered FOCS languages with different capabilities. That is probably much more fun to debug on MacOS. And leave the bugs which were in the old code as they were. Also just think about the long term confusion I could add with that.
Any code or patches in anything posted here is released under the CC and GPL licences in use for the FO project.
Look, ma... four combat bouts!
Look, ma... four combat bouts!