Roadmap updated with completed/moved items.

A lot of progress has been made over the past couple months with 097. I am rather happy with that myself. Nothing extremely "code breaking" for scripters (well, cept the module change, which someone has already released a nice auto-updater for that!). And several new features, fixed issues that will help a lot also with 096 additions that was put in.

So feel free to begin testing 097 openly, especially after the 8-1 release. We've done a big crash fix, and will be releasing a new bin very soon for beta.

MuadDib wrote:Roadmap updated with completed/moved items.

A lot of progress has been made over the past couple months with 097. I am rather happy with that myself. Nothing extremely "code breaking" for scripters (well, cept the module change, which someone has already released a nice auto-updater for that!). And several new features, fixed issues that will help a lot also with 096 additions that was put in.

So feel free to begin testing 097 openly, especially after the 8-1 release. We've done a big crash fix, and will be releasing a new bin very soon for beta.

you are doing a very good job (especially for repoutation system hooks ), but we are expecting fix on memory leaks too

Aye, the memory leaks involved in the cfgfile.em command is definately something on our list. Shini has the most experience in that area of the core, but he has been pretty busy irl. If I can catch some time with him, might try finding out what's going on with the system, and see if I can get time to look into also. Can't promise I can, cuz busy as crap too, but we'll see.

There has also been several fixes involving memory issues not yet released also, so we are making progress on those nasty buggers

MuadDib wrote:Aye, the memory leaks involved in the cfgfile.em command is definately something on our list.

in this case it's more a question of concepting than of scripting. on shard side this problem can be "solved" just by using data files instead of modifying cfg's on runtime.

Shinigami

Yes Shini, but isn't that just a workaround rather than a fix? If modifying cfgs is still allowed by the core then the memory leak still needs to be fixed I would think.

Otherwise the best course of action would be to remove the ability to change cfg files from the core. That would not be my favourite choice.