[Release] Id Tool 6.3_02 Hotfix

[IceTrailer]

Id Tool 6.3_02 (Hotfix) by IceTrailer

Instruction

This tool offers an efficient way to generate id lists from your .NOS files. It is possible to produce lists containing act descriptions, items, maps, monsters (NPCs) and skills.
The upcoming version is currently under development in C# .NET and will go open source when its progress is far enough and when most things are implemented.
The GUI version will not be maintained anymore since it will be replaced with the upcoming version release but you can still download and use it.
It is considered to start a new GUI project on top of the CLI tool.

How to use

To get started, configure the preferred language (English/German) and design layout (light/dark) initially. Once you configured, switch over to the "List creator" page and select the desired id list type (e. g. "Item").

Now you have two ways to continue. If you only like to generate usual id lists (with the scheme "<id> <translation>"), just click "Extract". But you may also try out the new personalization tool, just pick any items you would like to add to scheme from the right element box or if you would like to get any supported information, click "Add all" button. Now click "Extract" and wait some time.

The generating duration depends on the id list type you selected and your computer specs. On my computer it normally takes 1-2 seconds maximum.

Download (x64)

The download is located below the thread, as attachment.
Put content of Qt_Required_Files.zip into the folder of the extracted Nt_Id_Tool_XX.zip.
To run this software, Visual C++ 2017 x64 Redistributable is needed, it can be found .

Screenshot


Recent changes
Old GUI version

• Added new item element to extract: level requirement!
• Fixed filter bug
• Added new filter for item types (beta, better filter system now) please report bugs here!
• some performance improvements
• reimplemented sorting
• Added new file output options (now txt, csv, html) - ()
• possibility to change ui language
• kind of AI for detecting .NOS files
• new UI, light and dark design
• already decrypted data are not needed anymore (see Instruction)
• personalized extraction and changing the output format

 Upcoming features

Upcoming features
New CLI version

• new C# .NET Core console project (will replace GUI), good for automation tasks
• custom parsing definitions with if then conditions (input e.g. via types/item.json*)
• .NOS file caching
• open source access with option to contribute (following soon!)
• new item editor - will do later

*

 Custom parsing definitions (with conditions) example

Custom parsing definitions (with conditions) example

If there are values inside a .dat file of NSgtdData.NOS, you can define this as parsing definition inside the dedicated file types/<type>.json. This currently works for the types item, map_id, map_point and monster.


The parameter is never zero and will hereby start with 1.

 Default parsing definition

Default parsing definition
The default parsing definition looks like the following JSON string, e.g. file types/item.json

    {
      "Identifier": "isUnisex",
      "Name": "IsUnisex",
      "Description": "Represents the boolean value whether the item is unisex",
      "LineHeader": "FLAG",
      "Parameter": 16
    },

which means, translated to human language:

If the parser reaches a line, beginning with <LineHeader> (FLAG), take the 16th parameter of it as value for a new parsing definition with identifier "isUnisex".

 Simple If Then parsing definition

Simple If Then parsing definition
The simple If Then parsing definition looks like the following JSON string, inside e.g. file types/item.json

    {
      "Identifier": "equipmentType",
      "Name": "EquipmentType",
      "Description": "Represents the equipment type of the item e.g. 0 = MainWeapon",
      "LineHeader": "INDEX",
      "Parameter": 3,
      "Condition": {
        "IfValue": "-1",
        "ThenValue": "0"
      }
    }

which means, translated to human language:

If the parser reaches a line, beginning with <LineHeader> (INDEX), take the third parameter of it as value for a new parsing definition with identifier "equipmentType".
If the value is "-1", then use value "0" instead.

 Enhanced If Then parsing definition

Enhanced If Then parsing definition
The enhanced If Then parsing definition looks like the following JSON string, inside e.g. file types/item.json

    {
      "Identifier": "sex",
      "Name": "Sex",
      "Description": "Represents the value sex requirement with Male=0, Female=1, Unisex=2",
      "LineHeader": "FLAG",
      "Parameter": 21,
      "Condition": {
        "Identifier": "isUnisex",
        "IfValue": "1",
        "ThenValue": "2"
      }
    }

which means, translated to human language:

If the parser reaches a line, beginning with <LineHeader> (FLAG), take the 21th parameter of it as value for a new parsing definition with identifier "sex".
If the value of (another) parsing definition with identifier "isUnisex" is "1", then use value "2" instead.

 Allowed Values parsing definition

Allowed Values parsing definition
The Allowed Values parsing definition looks like the following JSON string, inside e.g. file types/item.json

    {
      "Identifier": "levelMinimum",
      "Name": "LevelMinimum",
      "Description": "Represents the level minimum to use the item e.g. 85",
      "LineHeader": "DATA",
      "Parameter": 1,
      "Condition": {
        "Identifier": "itemType",
        "AllowedValues": [ "0", "1", "2", "3" ],
        "DefaultValue": "0"
      }
    }

which means, translated to human language:

If the parser reaches a line, beginning with <LineHeader> (DATA), take the first parameter of it as value for a new parsing definition with identifier "levelMinimum".
If the value of (another) parsing definition with identifier "itemType" is not in [ 0, 1, 2, 3 ], then use default value 0 instead.

Notes:
One goal of the project is to find the meaning of any .dat file parameter.
So, the upcoming releasees will contain predefined custom parsing definitions.

Currently, the following .dat files do support custom parsing definitions Item, MapIdData, MapPointData, Monster.

Contributions are welcome and I will inform you as soon as you can do something for the project.
Ideas, suggestions can then be created as issue in the code repo.

Currently, if you have any idea or suggestions, feel free to send me or post it as thread answer.

[Yaksha00]

Vielen Dank sk8ter08

Dies würd uns Weiterhelfen die Files Jetzt auf Trap Zubringen so etwas hab Ich Gesucht

PS: Fast alles Ist implementiert Famsystem Fehlt Debus und Buffs und dies war es auch

Mfg Yaksha00

[iArtrix]

Nice job, you create tool for items and skills?

[IceTrailer]

Originally Posted by iArtrix

Nice job, you create tool for items and skills?

If someone tells me which the second parameter in Item.dat means :P

VNUM 1 70

e/
Done for Skill.dat
(see first post)

[Paint3r]

Originally Posted by sk8ter08

If someone tells me which the second parameter in Item.dat means :P




e/
Done for Skill.dat
(see first post)

Der Preis ( wenn man rechtsklick auf das item drückt)

[Xqlusiv]

Respekt an dich perfekte Arbeit !

[IceTrailer]

Da Langeweile, Stream während ich die Item List fertig mach

[_RowLegend_]

Wer hat den Thread downvoted. Gleich mal upvoten. Immer diese neider hier haha

[IceTrailer]

Update v2.0: Die Listen werden nun nach den IDs absteigend sortiert. Zuvor wurden die durcheinander generiert.



BTW: WORKS WITH ANY LANGUAGE FILES!



// Working on a Map ID List Creator

See

[|Marlboro|]

Danke dir das geile Update.
Das Teil tut genau das was es machen soll und hat mir meine Arbeit um einiges erleichtert.

Hut ab

[IceTrailer]

Update v3.0: Ihr könnt jetzt noch zusätzlich Map ID Listen erstellen.

[-Azra-]

Herzlichen Dank.

Ich liebe dich. ♥

[Sarcazm.]

Sieht nicht schlecht aus, werde es zwar nicht benutzen, da ich ein fauler Sack bin, aber gj.
Frage mich trotzdem, warum man der Community hier überhaupt noch irgendwas "umsonst" darlegt.

Gruß

[iArtrix]

#========================================================
	VNUM	5136	5000
	NAME	zts8635e
	INDEX	1	4	0	0	***	-1
	TYPE	0	0
	FLAG	0	0	0	0	1	0	0	0	0	0	0	1	0	0	0	0	0	0	0
	DATA	0	0	0	0	0	0	0	0	0	0	0	0	0	0	0	0	0	0	0	0
	BUFF	0	0	0	0	0	0	0	0	0	0	0	0	0	0	0	0	0	0	0	0	0	0	0	0	0
	LINEDESC	4
zts8636e
	END

Add *** value to list this is Image ID.

[erh4n]

Wozu sind diese codes hilfreich? Fürs Injecten oder was mach ich damit^^