1. How about you offer help if you want work done?
   
2. It is usually wise to not sound quite as annoying/condescending/dismissive when you want help.
   
3. You use NPatch. Not only does that strongly imply you're very much in the wrong forum, but VK has also officially admitted to not doing any bugtesting before release. Therefore, it is highly unlikely your game or mod will ever be in a state that could be considered "bug-free", and, as such, your experience fighting errors is not representative of the average user.
   In other words: We cannot rule out all problems you're having wouldn't be gone if you used a properly developed patch, and, as such, it'd be silly to alter a provenly working tool just to accommodate an environment that is broken by default.
   
4. On the same note, independent from the fact that I rather doubt NPatch itself handles NPatch's new armor types and countries well, VK is known for randomly and uselessly changing tag names around. It is impossible to handle any part of his work, because what is CountryTagFoo= today might be CountryTagBarBlueMoon= tomorrow.
   
5. As the wise one pointed out, if you seriously got that many errors, the INI Checker is the least of your problems. It sounds like you don't even have the most minor of clues what you're doing and rely on the INI Checker to fix your guesswork. That is not the type of modding we are promoting and supporting, and, as such, I rather doubt D would re-code his tool in a way that would basically make it worse than TibEd in its implications.
   
6. Lastly, as if all of the general problems above weren't enough, your ideas of everything are naive at best, and delusional at worst:
   Code cannot determine intent. Independent from the massive logic/database that would be necessary to even find words that could potentially be typos, how would the program auto-fix them?
   If you have "AARateo=", is that a typo of "AARatio=" or "AARate="?
   If you have Arm=, is that the flag Arm=, or a truncated Armor=?
   If you have Armor=, is that Armor=, or a truncated ArmorAircraftMult=, or a truncated ArmorBuildingsMult, or a truncated ArmorDefensesMult=, or a truncated ArmorInfantryMult=, or a truncated ArmorUnitsMult= or a truncated Armory=?
   
   Not to mention the retardedness of suggesting to remove unmatched warheads from the [Warheads] list.
   What if the list entry is correct, and the warhead itself is misspelled? e.g. [Warheads].900=KaboomWH and [KabommWH]. Then instead of making sure the user makes it right, you fuck up the code more by not only removing a clear indicator there is confusion there, but also by leaving a Warhead unreferenced in the Warheads list, breaking game and map functions, which will be irrelevant anyway, because if any weapon correctly referenced KabookWH, there'll be an error anyway.
   Of course, the user will fix the typo, think all is well now, not knowing that your genius little fix removed the list entry, setting it up for failure.
   Or, the other way around, the list entry is incorrect, and the warhead is fine - the warhead will likely work for a little while because not all functions rely on the list. But when the time comes and the game breaks, the user never even has a chance to find out where the problem is from, because the Checker doesn't cry about a wrong list entry - there is none, after all. If the modder does realize the problem is with the list, he's left to wonder whether he forgot to list it in the first place, or the Checker quietly fucked up his code.

Quote:When you press, the "Check" button, there should be diffrence/more options:
- Check if weapon dont exist on unit/bulding
- Check if a projectile is missing
- Check if a warhead is missing
- Check if there is a code that is misspelled/dont exist

Quote:- Check if a Deathweapon is missing

Quote:Also:
- Be able to fix problem itself, exempel if some warhead exist in [Warheads] but not anywere else, it should be erased

Quote:- Save all errors in a txt file(so you can use the search funktion, I got like 1000 errors)

Quote:- Handle Npatchs new armor types and countries

(06.06.2009, 20:00:40)DCoder Wrote:

Quote:When you press, the "Check" button, there should be diffrence/more options:
- Check if weapon dont exist on unit/bulding
- Check if a projectile is missing
- Check if a warhead is missing
- Check if there is a code that is misspelled/dont exist

Already works.

Quote:Besides, the NPatch can fuck off with it causing unexplainable errors.

(06.06.2009, 21:32:12)Guest Wrote:

(06.06.2009, 20:00:40)DCoder Wrote:

Quote:When you press, the "Check" button, there should be diffrence/more options:
- Check if weapon dont exist on unit/bulding
- Check if a projectile is missing
- Check if a warhead is missing
- Check if there is a code that is misspelled/dont exist

Already works.

Read the first sentense of my quote. Honestly that is the only importat thing that need to be added imo

(06.06.2009, 21:32:12)Guest Wrote: Also Ren, 0_o

(06.06.2009, 21:32:12)Guest Wrote: Dont go offtopic, if you dont like NPatch you can go to revora and complain non-stop

Quote:damn man Ren you are an idiot, I post some suggestions to DCoder, and from no were you come and attack me
The one who is bitching and whining is you.
And this topic is NOT about NPatch, fuck NPatch dont metion it again

Quote:

Quote:When you press, the "Check" button, there should be diffrence/more options:
Honestly that is the only importat thing that need to be added imo

What good are those options going to do? All the things you listed are causes for IE, and it's not like you save a lot of time by (de)activating them?

• Half of your feature suggestions have, according to the author, been in the tool for at least 5 years
  
• Your direct "new" suggestions are obviously infeasible and only serve to deteriorate the quality of the tool
  
• You were incapable of finding the boldly labeled "DCoder's Coding Realm"
  
• After multiple posts by multiple people, you still don't grasp that your use of NPatch has all but invalidated your post, because you are basically admitting to having a random error generator in your game, thus making NPatch very much on topic
  

• Your mod is broken by default because you use NPatch.
  
• Your mod is broken beyond recognition anyway, because if it wasn't, you wouldn't get 1000 errors.
  
• If your mod is that broken, the central problem are you and your coding abilities, not INI Checker's ability to find and correct the errors.
  
• Half of your suggestions are worthless, because they're already in there.
  
• Most of the others are worthless because they are either a) not programatically possible, or b) would be just plain dumb or undesirable.