this behaviour seem to be a bug.
When using Game::World.del() after having a world loaded, it automatically calls the Game::World.save() on all objects, I wouldn't expect a world I told to delete to save without me actually telling it by calling Game::World.save(file);

Hi Esenthel, would you have any idea on how we could solve this issues that Zervox mentioned above? Its something really urgent for us and we having the same issues which you can see on the following thread: http://www.esenthel.com/community/showth...p?tid=6669

Appreciate it sir if you could help us on this issues. Thanks in advance

Hi, that's not a bug, it's made on purpose, for example if your world is dynamic (like in Ineisis) then when releasing the world, all changes to the areas must be flushed to the disk, hence all areas and objects have 'save' called on world deletion.

My question then would still be why, this should atleast be possible to disable when you use projects which has static worlds.

I agree with Zervox here. It should be made optional whether save is called or not. A simple boolean argument for del() should suffice.