need help reading .ini file
Re: need help reading .ini file
Yes, names.txt should slowly be phased out of existence. Patches to add names to .ini files that are missing them, and removing unused names from names.txt would be most welcome.
Re: need help reading .ini file
First step is to make patch for ini files and attach it to ticket in track. If you want to do it do it or I can do it.crab_ wrote:Hello.
I can turn names of cyborgs from names.txt into templates.ini, if someone will write codes it in hardcode
I make pull request with little phase After move of templates I will make some hand clean.Per wrote:Yes, names.txt should slowly be phased out of existence. Patches to add names to .ini files that are missing them, and removing unused names from names.txt would be most welcome.
*.po files has a lot of entries to names (#: data/base/messages/strings/names.txt:783) may be we should delete this comments?
http://addons.wz2100.net/ developer
-
- Inactive
- Posts: 1695
- Joined: 01 Sep 2006, 19:17
Re: need help reading .ini file
Those will be automatically removed once the files get refreshed for master/3.2.Duha wrote:*.po files has a lot of entries to names (#: data/base/messages/strings/names.txt:783) may be we should delete this comments?
We want information... information... information.
Re: need help reading .ini file
Do you plan to accept pull request with remove default values? https://github.com/Warzone2100/warzone2100/pull/44Per wrote:Yes, names.txt should slowly be phased out of existence. Patches to add names to .ini files that are missing them, and removing unused names from names.txt would be most welcome.
Spoiler:
http://addons.wz2100.net/ developer
Re: need help reading .ini file
I think that has already been merged as part of https://github.com/Warzone2100/warzone2100/pull/43 ?
You should squash and clean your pull requests, I think. Or post changes as a patch on the bug tracker. When a pull request says "Cjkjvfnby wants to merge 45 commits into Warzone2100:master", I become rather hesitant to merge it...
You should squash and clean your pull requests, I think. Or post changes as a patch on the bug tracker. When a pull request says "Cjkjvfnby wants to merge 45 commits into Warzone2100:master", I become rather hesitant to merge it...
Re: need help reading .ini file
Not this is another part.Per wrote:I think that has already been merged as part of https://github.com/Warzone2100/warzone2100/pull/43 ?
Pull request are pretty if they are just from master. After merging into it updates from master they are became a mess. Only 21 commit of pull request belongs to this branch other are taken from master.You should squash and clean your pull requests, I think. Or post changes as a patch on the bug tracker. When a pull request says "Cjkjvfnby wants to merge 45 commits into Warzone2100:master", I become rather hesitant to merge it...
Please reject github pull request. I have done track ticket #4100
http://addons.wz2100.net/ developer
Re: need help reading .ini file
I think about sorting ini files.
two phases of sorting:
1. sort by ID (ZNULL* first others by abc).
2. sort keys in same order as they described in header.
reason:
1. little improvement of readability
2. my tools for work with ini files does not support order. Adding new field convert patch to real mess.
I create patch with moving names to templates (ini files only) (#4106)
Ticket with removing default values is still waiting (#4100)
PS. Looks like ticket where per is author broken for me:
{9} Commits per author
two phases of sorting:
1. sort by ID (ZNULL* first others by abc).
2. sort keys in same order as they described in header.
reason:
1. little improvement of readability
2. my tools for work with ini files does not support order. Adding new field convert patch to real mess.
I create patch with moving names to templates (ini files only) (#4106)
Ticket with removing default values is still waiting (#4100)
PS. Looks like ticket where per is author broken for me:
{9} Commits per author
http://addons.wz2100.net/ developer
Re: need help reading .ini file
How did pie files resolved for mods?
base + modpies or base + mp + modpies?
base + modpies or base + mp + modpies?
http://addons.wz2100.net/ developer
Re: need help reading .ini file
There's single physfs instance, which first gets populated from base, then, if we are playing skirmish or multiplayer, mp gets written over it. Whatever files are present after that are used.
There's nothing special about PIE files in this process.
There's nothing special about PIE files in this process.
Maps | Tower Defense | NullBot AI | More NullBot AI | Scavs | More Scavs | Tilesets | Walkthrough | JSCam
Re: need help reading .ini file
Hello.
What you think about idea: add 'description' field to each component in game?
This description can be shown in unit design screen
What you think about idea: add 'description' field to each component in game?
This description can be shown in unit design screen
Warzone2100 Guide - http://betaguide.wz2100.net/
Re: need help reading .ini file
It is possible to make description based on component type.crab_ wrote:Hello.
What you think about idea: add 'description' field to each component in game?
This description can be shown in unit design screen
http://addons.wz2100.net/ developer