Welcome!

Join our community of MMO enthusiasts and game developers! By registering, you'll gain access to discussions on the latest developments in MMO server files and collaborate with like-minded individuals. Join us today and unlock the potential of MMO server development!

Join Today!

sELedit - Simple Element Editor (unstable)

Status
Not open for further replies.
PW Dev <3
Joined
Feb 28, 2011
Messages
722
Reaction score
117
Did I ask you?
Just wanted to make sure before I start re-adding ~2k element entries to 1.4.4 data and it will be useless again since they release 1.4.5 soon :glare:

Look at the post ronny posted, I was actually trying to help.
 
Banned
Banned
Joined
Aug 10, 2011
Messages
201
Reaction score
54
Can anyone post the config for elements.data v28 :/
 
Joined
Jan 6, 2010
Messages
744
Reaction score
1,051
Major Update for sELedit

  • name scheme and parameters for *.cfg files and *.rules files has been changed
  • element structure diff tool has been added (GUI for creating rules)

Configuration Files
Name scheme: PW_1.4.4_v63.cfg
PW -> identifies game
1.4.4 -> identifies the game version (can also be 144 or 1-4-4 or...)
v63 -> identifies the version of the elements.data which belongs to this configuration file

Parameters: the version and signature are no longer part of the offset from the first list, which means the offset must be reduced by 4 bytes

from:
Code:
001 - Equipment Addons
[COLOR="#FF0000"]4[/COLOR]
ID;Name;Number of Values;Value 1;Value 2;Value 3
int32;wstring:64;int32;int32;int32;int32
to:
Code:
001 - Equipment Addons
[COLOR="#FF0000"]0[/COLOR]
ID;Name;Number of Values;Value 1;Value 2;Value 3
int32;wstring:64;int32;int32;int32;int32

Rules Files
Name scheme: PW_v12 = PW_v7.rules
PW -> identifies the source game
v12 -> identifies the version of the source elements.data file
= -> fixed delimiter
PW -> identifies the target game
v7 -> identifies the version of the target elements.data file

Parameters: all rule files must have a SETVERSION and SETSIGNATURE entry. Those keys must contain the values of the target elements.data file!

Code:
#############################
#### RULES FOR v12 -> v7 ####
#############################

[COLOR="#FF0000"]SETVERSION|7
SETSIGNATURE|12288[/COLOR]

REPLACEOFFSET:0|
REPLACEOFFSET:20|
REPLACEOFFSET:100|

REMOVEVALUE:54:3

REMOVEVALUE:69:7

REMOVEVALUE:94:8

Element Structure Diff
1. Load Files

  • load the base/target file (i.e. raw pwi v63)
  • load the recent/source file (i.e. raw pwi v69)
  • both files requires consistent configuration files
  • configuration files are consistent when they don't differ in their common lists/fields structure
  • ronny1982 - sELedit - Simple Element Editor (unstable) - RaGEZONE Forums

2. Import Rules

  • assume you have base file v63 and recent file v69
  • if you already have a rules file for v66 -> v63 you can click the import button to apply those rules
  • you can import from multiple rules files, i.e. rules for v69 -> v66 and rules for v66 -> v63

3. Remove Lists

  • sometimes the recent file has additional lists
  • if the left comparison panel stays blank when selecting a list this means the list appears in the recent file, but is missing in the base file
  • in that case we have to add a rule to remove the selected list
  • just check the box to the right of the list selection
  • ronny1982 - sELedit - Simple Element Editor (unstable) - RaGEZONE Forums

4. Replace Offsets

  • most lists have blank offset values
  • some suspicious lists (0, 20, 100) have offset values
  • use the radio button to choose which offset for a list should be used
  • if your base/target version is <= 7 you have to use the base file offset for lists 0, 20, 100
  • if your base/target version is > 7 there is no need to use the base file offset (not confirmed since i don't have a server)
  • ronny1982 - sELedit - Simple Element Editor (unstable) - RaGEZONE Forums

5. Remove Fields

  • this is the most difficult part
  • some lists of the base/target file will have less fields than the recent/source file
  • select a list and watch the left comparison panel
  • the column header Base Fields (x) and Recent Fields (y) shows the number of available fields (x, y)
  • when the number is different (x<y) then you have to remove some fields from the recent/source file
  • there is an additional column called mismatches which helps you to rate the fields equation
  • to explain how mismatches works a simple example
  • assume you have the list weapons containing a field 'atk'
  • the list weapons holds 1300 elements (the real number of elements in each list can be found in the brackets after the list name)
  • mismatches will scan each weapons field 'atk' from base/target file and compare it to the weapons 'atk' from the recent/source file
  • if a weapon from base/target file has a different value than the recent/source file, the mismatch counter will be increased by one (in worst case 1300 for our example)
  • so how does mismatches help us to rate fields?
  • more mismatches increases the possibility that the base/target field is not the same as the recent/source field (if mismatches = real number of elements (-> all values are different), possibility is realy high that fields don't belong to each other)
  • in that case you could check the box for that field in the DEL column
  • in case you wanna compare the values on your own you can click the Details button
  • all values (i.e. the 'atk' field of all weapons) will be listed in the right comparison panel
  • the difference of field numbers between base-recent must be the same as the number of checked boxes in the DEL column (i.e. base: 5 fields, recent: 8 fields -> exactly 3 fields must be removed)
  • ronny1982 - sELedit - Simple Element Editor (unstable) - RaGEZONE Forums

6. Export Rules

  • when everything is done you can click the View Rules button to view all rules in plain text
  • the rules can be saved by clicking the Export Rules button
  • it is strongly recommend to keep the file name suggestion
  • ronny1982 - sELedit - Simple Element Editor (unstable) - RaGEZONE Forums
 

Attachments

You must be registered for see attachments list
Last edited:
Joined
Jan 6, 2010
Messages
744
Reaction score
1,051
About Configuration Files...

Since many people request configuration files, here some statements...

Some rough hints how you can basically analyze them:
*would be nice if someone could make a detailed guide with pictures

  • open the latest available elements.data file in sELedit (for comparsion)
  • check the version of the new elements.data file (sELedit->Tools->EL Version)
  • create a copy of the latest configuration file and name it related to the new el version (i.e. PW_1.4.5_v66.cfg -> PW_1.4.5_v69.cfg)
  • open the copied configuration with an text editor
  • next is trial & error, we need to find out which lists have changed
  • set the first number in the configuration file to maybe 10 (this will tell sELedit to only load 10 lists)
  • save the configuration file, open a another instance of sELedit and load the newest elements.data file
  • if everything goes well, 10 lists will be loaded, walk through each list and check if the values are ok
  • check the behavior:
    1. if a list seems not ok, or an error occurred during loading go back to the text editor with the configuration file and reduce the number to maybe 5 and repeat until you found the list causing errors
    2. if list seems ok and no error occurred go back to the text editor with the configuration file and increase the number to maybe 20 and repeat the check
  • when you found a list causing errors you need to check the new elements.data file in a hex editor
  • take a look into sELedit with the old elements.data and go to the list causing errors in the new elements.data
  • take the id (or other distinct values) of first and second item in the list and try to locate them in the hexeditor
  • now compare the entrys between the hexeditor and sELedit (old elements.data)
  • if you locate the new data types in the list insert them to the configuration file, increase the list number at the top of the file and reload the new elements.data in the second instance of sELedit

To encourage people making configuration files i've added an experimental feature to sELedit, which analyze a new elements.data file by using an older configuration file.

  • download latest sELedit
  • open sELedit->Tools->Config Editor
  • in the Configuration Editor goto File->Load and open the latest configuration file
  • now goto File->Scan Sequel and open the newest elements.data file
  • if list 99 popup, click yes (hope pw will not change that list soon)
  • if everything works, a log file will be opened, viewing info about each list
  • look out for the "Changed entry size", in these lists you need to add fields (i.e. size +12 -> add 3x int32, or 3x float, or byte:12,...)
  • check the end of the log file, if bytes are left, this might be an indicator for additional lists

deep-sca - sELedit - Simple Element Editor (unstable) - RaGEZONE Forums

this report shows information which will save you time and effort finding the changes, but you still need to edit the configuration file and also use a hex editor for structuring new lists...
 

Attachments

You must be registered for see attachments list
Initiate Mage
Joined
Jan 17, 2013
Messages
1
Reaction score
0
Sorry, the page you requested was not found. Return to the .
If you would like to contact us regarding this, please click .
 
Status
Not open for further replies.
Back
Top