L2J Server

Both of them complain about deleted custom spawns, not customizing of the base spawnlist.

janiii wrote:i dont think customizing the spawnlist is junk. it is a normal feature of a customizable l2j server. i dont agree with removing the not_spawned table too. you cannot directly change the sql files from svn when you change the spawns. that is why there was the table - to control the removed original spawns and be able to update the sql files and the database with those changes.

Yes, that is what I mean. Thanks janiii.

In one of our servers, we have lot of custom zones, farm zones... with spawns. In towns also custom spawns. After lastest update and removed nonspawn table, all was broken. Well, life is hard and we restore old spawns, but in few zones we need to remove mobs and their spawn has removed from original spawnlist table, so on svn update we need to use software like winmerge to see diffs in spawnlist and update it by hand. It is not good.


Well, last method was not good (added new record in nonspawn table and in custom_spawnlist record stay), but new method (removed nonspawn table and delete record from original spawnlist table) is not good as well. Sorry to say that, but for me it is truth.

lol? how could you use notspawned table for disabling original l2j spawns?? spawnlist.sql does not contains IDs so if someone from l2jdp add few spawns at begin all ids will be shifted

I'm working on moving the spawnlist to xml, made the xsd and the basic xml already, now just have to parse the sql and change spawntable. And figure out how to deal with custom spawnlist.
Edit: core part is done, all that's left is to convert the spawnlist table to XML and test it