Quote:
|
when you make some modification in svmap [impacting] npc [or] monster
|
that's correct; Monster/Monster.sdata & Npc/NpcQuest.sdata are involved in some operations managed during edition of .svmap files (monster.mon & npc.mon are also loaded but never changed).
using Monster Areas, or Monsters panels and double-clicking a monster name will open the monster information and thus will modify (if changes are made and dialog validated) monster.sdata; similary using NPC panel & dbl-clicking a NPC record will allow to edit the NPC information in NpcQuest.sdata.
these files (if modified) use a "dirty file" indicator in the workspace, but indeed, they must be opened and saved by the user.
note that previous release allow these shared files to be closed re-opened w/o losing the changes (if closed w/o saving them); it is changed in 0.7.5.4 for some of them (another side effect), the file state is now resetted when dirty file are closed w/o chosing the save the changes (they are marked to force a reload at next access); this change still allow to opened a NpcSkill.sdata or Monster.sdata marked as dirty by the svmap editor, but changes must be saved before or during closing them.
also note that svmap editor loads the monster.sdata and not the monsterEx.sdata file; consequently if monsterEx exists it will not contain the changes (and since the monster definition is loaded (from monster.sdata)) edition of extended data won't be possible until next loading of workspace or reload-opening of the file (Ctrl pressed while double clicking "monster.sdata" file in workspace).
all these points must be fixed.
an option to save edited files when the svmap fileis saved (or even simply closed if it's the sole responsible of the changes) would make sense; I will study that (customizing standard file dialogs could be a way to manage "linked saves").
@Soont
as for some .sdata files edited by svmap editor, the edition of safe zones actually change the content of world/TacticsZone.zon and that file is not automatically saved when the svmap editor is closed.
so please be sure to open & saved the TacticsZone.zon after you edit its content.
if it was done, additional tests are required to validate that this file is actually used by client and actually perform what we suppose it does.
rigorous tests of (old) jungle zones should be performed, including deleting zones and verify that PvP can be performed (near OI access for instance; portals access are protected by a transparent shape that can be crossed in a single way) and also changing the size of these zones to verify impact. until now I was not able to manage these tests (issue with a server component).