Hello. Maybe this question is straightforward, but I couldn't find an answer anywhere. I would ask 2 questions, but basically it's one. What is data structure of .svmap. I mean bytes structure? Or is it possible to parse this file somehow in some readable file type like .json/.xml/.csv ?
Example:
To extract 0.svmap into its respective CSV files in command prompt enter:
"Map_csv 0"
To re-combine it back into svmap type:
"Map_svmap 0"
What is data structure of .svmap. I mean bytes structure?
Or is it possible to parse this file somehow in some readable file type like .json/.xml/.csv ?
I thought the .svmap format was already published somewhere but I failed to find it. A new post is available .
Making the file human-redable is up to you. Nota .json & .xml can be used since they offer all required flexibility; .csv cannot be used since it's only able to manage identical fixed records (meaning quite nothing).
Cannot edit while editing a skill Fixrange field,This made it impossible for me to modify the skill's time plan,I hope the author has time to update it. Sorry for my poor English.
Continuous skill fields,【RrevSkillID】 Time field ,[Fixrange]。Cannot find editable place in tool。
The tailored skill editors of v.0.9.0.5 indeed don't give access to the [FixRange] attribute; however the "Raw Skills" tab - that displays all attributes (all columns of the equivalent DB table) - does give access to the field: select the line of interest, right-scroll to the antepenultimate column, move mouse over that column, type-in F2 key (or click+release++move), change value.
It appears that FixRange is used by several Noos skills; a column is do added to the Noos editor to allow direct change of it.
(The tailored dialogs of the not-noos skills still do NOT display this field.)
Quote:
Originally Posted by melvinbk
We encounter a problem with the recording of the DBMonsterData.Sdata.
The size [desreases] from 3,665,552 bytes to 268,560 bytes and the file becomes unreadable.
The saving of DBMonsterData.Sdata was bugged (the data are saved using Monster.sdata format; the DBMonsterText_???.sdata file was not generated).
The issue is fixed.
@: A potential issue on 0.8.0.3 was not checked.
If the use of version 0.9.0.x was impossible, please indicate it.
The support of v.0.8.x cannot be guaranteed.
@: further analysis - and possibly fixes - has to be done on NPCQuest.sData.
Take care of yourself and everyone you don't know.
Castor.
release 0.9.0.6
Bugs Fix:
* The saving of BinarySData/DBMonsterData.sdata was bugged.
Changes:
* The "Noos editor" (while editing Skill.sdata or BDSkillData.sdata) now displays the [FixRange] attribute.
* The size of images of gears or weapons displayed while editing Items.sdata is restored (enlarged).
[IMG]Generated now skill.sql Unable to query effectively. The generated SQL has no skill name.Rrevskilldid and fixrange, shstudio 0.9.0.6.exe can be edited effectively, but the generated SQL still has problems. Thank the author for his powerful modification tool, which is really great.[/IMG]
The tailored skill editors of v.0.9.0.5 indeed don't give access to the [FixRange] attribute; however the "Raw Skills" tab - that displays all attributes (all columns of the equivalent DB table) - does give access to the field: select the line of interest, right-scroll to the antepenultimate column, move mouse over that column, type-in F2 key (or click+release++move), change value.
It appears that FixRange is used by several Noos skills; a column is do added to the Noos editor to allow direct change of it.
(The tailored dialogs of the not-noos skills still do NOT display this field.)
The saving of DBMonsterData.Sdata was bugged (the data are saved using Monster.sdata format; the DBMonsterText_???.sdata file was not generated).
The issue is fixed.
@: A potential issue on 0.8.0.3 was not checked.
If the use of version 0.9.0.x was impossible, please indicate it.
The support of v.0.8.x cannot be guaranteed.
@: further analysis - and possibly fixes - has to be done on NPCQuest.sData.
Take care of yourself and everyone you don't know.
Castor.
release 0.9.0.6
Bugs Fix:
* The saving of BinarySData/DBMonsterData.sdata was bugged.
Changes:
* The "Noos editor" (while editing Skill.sdata or BDSkillData.sdata) now displays the [FixRange] attribute.
* The size of images of gears or weapons displayed while editing Items.sdata is restored (enlarged).
Hello Castor ! First of all thank you
Tested your new release 0.9.0.6 and found few bugs :
1. Still After Save NPCQuest.sData crash ( or doesn't load anymore )
2. Scrolling fast crash the app
3. svmaps can't be loaded
4. Taking definitations from database (creating monsterEx.sdata) makes monster in chinese characters ( even i choose different language on start up )
Generated now skill.sql Unable to query effectively.
The generated SQL has no skill name.Rrevskilldid and fixrange, shstudio 0.9.0.6.exe
can be edited effectively, but the generated SQL still has problems.
OK, I'm not sure to clearly understand all details of your point, so let's comment several points and please answer all of them.
Your previous request was related to the [FixRange] field, so I hope you're not now claiming that fixrange should not exist.
You indicate that "The generated SQL has no foo, bar".
It is not clear if this is a description of the generated .sql file, or the error returned by the MSSQL engine when you execute the script (the provided img does not give answer since I don't read Chinese).
Regarding the Skill.sql file generated by the tool, it contains:
Code:
DELETE FROM [PS_GameDefs].[dbo].[Skills] WHERE SkillLevel<100;
GO
INSERT INTO [PS_GameDefs].[dbo].[Skills] (SkillID,SkillLevel,SkillName,Country,Attackfighter,Defensefighter,Patrolrogue,Shootrogue,Attackmage,Defensemage,PrevSkillID,ReqLevel,Grow,SkillPoint,TypeShow,TypeAttack,TypeEffect,TypeDetail,NeedWeapon1,NeedWeapon2,NeedWeapon3,NeedWeapon4,NeedWeapon5,NeedWeapon6,NeedWeapon7,NeedWeapon8,NeedWeapon9,NeedWeapon10,NeedWeapon11,NeedWeapon12,NeedWeapon13,NeedWeapon14,NeedWeapon15,Shield,SP,MP,ReadyTime,ResetTime,AttackRange,StateType,AttrType,[Disable],SuccessType,SuccessValue,TargetType,ApplyRange,MultiAttack,KeepTime,Weapon1,Weapon2,Weaponvalue,Bag,Arrow,DamageType,DamageHP,DamageSP,DamageMP,TimeDamageType,TimeDamageHP,TimeDamageSP,TimeDamageMP,AddDamageHP,AddDamageSP,AddDamageMP,AbilityType1,AbilityValue1,AbilityType2,AbilityValue2,AbilityType3,AbilityValue3,AbilityType4,AbilityValue4,AbilityType5,AbilityValue5,AbilityType6,AbilityValue6,AbilityType7,AbilityValue7,AbilityType8,AbilityValue8,AbilityType9,AbilityValue9,AbilityType10,AbilityValue10,HealHP,HealSP,HealMP,TimeHealHP,TimeHealSP,TimeHealMP,DefenceType,DefenceValue,LimitHP,FixRange,ChangeType,ChangeLevel,UpdateDate) VALUES
(1,1,6,1,0,1,0,0,0,0,1,0,1,1,0,0,4,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,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,0,0,0,0,0,0,23,10,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,0,0,0,0,0,GetDate()),
1) the [FixRange] field is declared in the list of updated fields and its value is provided.
2) the "Rrevskilldid" apparently has 2 typos. The BinarySData/DBNpcSkillData.sdata and BinarySData/DBSkillData.sdata files have a field named "prevskill"; the server-side PS_GameDefs.dbo.Skills table has a column named "PrevSkillID"
3) the [SkillName] column is present in the list of updated columns but no value are provided (the "(...)" part contains the names of 97 columns, the "values(...)" part contains only 96 values.
So:
- yes, there is an error preventing the update of the dbo.Skill table: the value of the skill name is missing (note that this value is useless for the server - except for readability) but declaring it and not providing a value is NOT valid).
- the script assumes that the column containing the value of the identifier of the skill that shall be used/activated prior to use the currrent one is named "PrevSkillID". If your dbo.Skill table uses another name, replace the "PrevSkillID" sentence in the .sql script with your name; or alternatively make the changes in your DB (the svr components don't care about that name; they use a stored proc to real all skill-details, so you can change a column name as long as you also apply the name in the SP).
my AP: re-insert skill name in dbo.Skills insert statements.
your AP: for such error related to sql scripts generated by the tool, it is NOT possible to fix issues, nor enhance features, without the full knowledge of the edited table. So if you still experience issue, you must provide the full structure (definition) of your table (possibly a few first lines of it).
Edit: you should remove the "SkillName," word from the skill.sql file and test it against your server to check the errors actually present. /Edit
Reminder on the context:
few tables are clearly detailed among our forums; because the need did not appear or because the effort was not made.
shStudio is based on the binary content of old tables; if you use recent tables a new distribution of new columns may be present, names may be different; this having been carried out by AGE or by the person who published the tables.
it is therefore essential to clearly indicate the structure of the tables not managed correctly by the tool.
Quote:
Originally Posted by [ADM]Beno™
Tested your new release 0.9.0.6 and found few bugs :
1. Still After Save NPC.sData crash ( or doesn't load anymore )
2. Scrolling fast crash the app
3. svmaps can't be loaded
4. Taking definitations from database (creating monsterEx.sdata) makes monster in chinese characters ( even i choose different language on start up )
0. I confirm that NPCQuest.sdata is corrupted after saving, fix will be delivered.
1. "NPC.sdata" does not exist.
2. Scrolling which list from which file under which conditions ?
3. Indeed, something was broken (additional information - not present in the file - was added to help design a visual editor, but the editor is not finished and the loading has been corrupted, this is not not a way to handle stuff).
4. The import from database imports all columns of the table, including the monster names.
There, names are changed to Chinese because your DB contain chinese names; the prefered langage chosen in appl doesn't matter.
After importing from database, you must use the tools/script "Import text fields from a language file" to change the names with the content of one of the BinarySData/DBMonsterText_???.sdata file. Note that if you don't have a v.6+ client with such file, or if you defined tailored names, you can (you must) export your names (1st item of tools/scripts) and re-import them later.
This problem does not exist in previous versions. For example, I want to add a new skill or modify the name of a skill. There is no skill name when generating SQL, which leads me to edit SQL again. Obviously not the best solution. The skill editor of 0803 version is very perfect, but it doesn't support languages of many countries. It must be used under English system. Thank the author for releasing this powerful modification tool. I'm sorry that my speech comes from Google translation.
The tailored skill editors of v.0.9.0.5 indeed don't give access to the [FixRange] attribute; however the "Raw Skills" tab - that displays all attributes (all columns of the equivalent DB table) - does give access to the field: select the line of interest, right-scroll to the antepenultimate column, move mouse over that column, type-in F2 key (or click+release++move), change value.
It appears that FixRange is used by several Noos skills; a column is do added to the Noos editor to allow direct change of it.
(The tailored dialogs of the not-noos skills still do NOT display this field.)
The saving of DBMonsterData.Sdata was bugged (the data are saved using Monster.sdata format; the DBMonsterText_???.sdata file was not generated).
The issue is fixed.
@: A potential issue on 0.8.0.3 was not checked.
If the use of version 0.9.0.x was impossible, please indicate it.
The support of v.0.8.x cannot be guaranteed.
@: further analysis - and possibly fixes - has to be done on NPCQuest.sData.
Take care of yourself and everyone you don't know.
Castor.
release 0.9.0.6
Bugs Fix:
* The saving of BinarySData/DBMonsterData.sdata was bugged.
Changes:
* The "Noos editor" (while editing Skill.sdata or BDSkillData.sdata) now displays the [FixRange] attribute.
* The size of images of gears or weapons displayed while editing Items.sdata is restored (enlarged).
With your method, I found a bug, which was modified and then restored to the initial state. You can try it.
The tailored skill editors of v.0.9.0.5 indeed don't give access to the [FixRange] attribute; however the "Raw Skills" tab - that displays all attributes (all columns of the equivalent DB table) - does give access to the field: select the line of interest, right-scroll to the antepenultimate column, move mouse over that column, type-in F2 key (or click+release++move), change value.With your method, I found a bug, which was modified and then restored to the initial state. You can try it.
A general problem to all Shaiya Studio versions i've discovered is about creating a new quest in-game is not working to attach with NPC... something is pretty weird
Hello, I'm having trouble saving binarysdata files, whenever I modify and save when I open again they are the same as they were before the grind, is there anything I can do to make this fixed?
Hello, I'm having trouble saving binarysdata files, whenever I modify and save when I open again they are the same as they were before the grind, is there anything I can do to make this fixed?
[Release] shStudio (multi-purposes editor) 02/05/2021 - Shaiya PServer Guides & Releases - 755 Replies Introducing Shaiya Studio, a multi-purposes editor.
Its purpose is to enable fast editing of clients and servers configuration files.
Update of May 4th, 2013:
This post was modified by November 2011 to present some features of the incoming - and still not released - version 0.7.5
The modifications of the interface of the new version (mainly the "multiple documents interface" and the concepts of workspace but also the possibility to browse & edit files from an unexpanded archive fle...
[Release / Update] shStudio 03/18/2011 - Shaiya PServer Guides & Releases - 1 Replies shStudio rel. 0.6.2 released
This post is only intended to inform you of the update of the tool (since "Edit" doesn't change its date), thank you for letting this thread die and ask your questions on the main thread.