- Thread starter rhasce
- Start date
Actually, the problem is with XmlSpawner. I have run into this multiple times. To be honest, I do not remember if I ever found a solution. However, as they are technically "warnings" and not errors, I pretty much let it slide.
The issue seems to be that during a World.Save event, the code in XmlSpawner has a save routine somewhere that must actually be creating an instance of creatures. Either that or the Tick event for spawns is somehow over-riding the freeze that is supposed to be placed on the world during Saves. I found most of the time these were located in Orc Camps or some other type of spawn such as this with several Mobiles.
I know that I have posted on several forums and in private message to people I consider to be "gurus" with XmlSpawner, and I honestly am unable to recall if there was ever any "fix" for this. Let me see if @tass23 or @Ravenwolfe remembers our previous conversations.
One thing I do remember might have fixed it was starting over with a new server. I think the code I was using was outdated. If you are unable to upgrade your XmlSpawner to match what is in the most recent Repo, or if doing so does not resolve it, we can have a look at a couple methods in your copy of the XmlSpawner, and see if we can find the culprit.
The issue seems to be that during a World.Save event, the code in XmlSpawner has a save routine somewhere that must actually be creating an instance of creatures. Either that or the Tick event for spawns is somehow over-riding the freeze that is supposed to be placed on the world during Saves. I found most of the time these were located in Orc Camps or some other type of spawn such as this with several Mobiles.
I know that I have posted on several forums and in private message to people I consider to be "gurus" with XmlSpawner, and I honestly am unable to recall if there was ever any "fix" for this. Let me see if @tass23 or @Ravenwolfe remembers our previous conversations.
One thing I do remember might have fixed it was starting over with a new server. I think the code I was using was outdated. If you are unable to upgrade your XmlSpawner to match what is in the most recent Repo, or if doing so does not resolve it, we can have a look at a couple methods in your copy of the XmlSpawner, and see if we can find the culprit.
OP
rhasce
Member
Yes, I remember we spoke about this a few years ago. I have never experienced this on The Expanse, but I have run into the issue with shards from others looking for fixes. A clean installation of Xmlspawner appeared to fix things, but I don't remember if any Saves were saved, since it was basically a brand new shard to begin with.
The long alternative would be to start with a new shard that has Xmlspawner installed and slowly port over your custom code(s) to see if/when it breaks the functionality again.
