SilentStorm wrote:While talking about Memory Usage of Aseco... Mine keeps shutting down every few days due to more than 32MiB of Memory used. I have to start it again which leaves it running just fine until it crashes again due to too much memory used. Any Ideas?

OS is Debian 4 btw and PHP is 5.2.0

Just out of curiosity, have you tried increasing the PHP mem limit? I typically set mine to 96mb, and even then experience crashes.

As far as mem usage goes, I've had the nagging thought that Aseco isn't clearing all the player data upon a player's disconnection... All the code seems to be perfectly fine, but certain manialink/widget displays carry over after a disconnect and reconnection (such as oliverde8's menu staying open to the previous tab).

nocturne wrote:
As far as mem usage goes, I've had the nagging thought that Aseco isn't clearing all the player data upon a player's disconnection... All the code seems to be perfectly fine, but certain manialink/widget displays carry over after a disconnect and reconnection (such as oliverde8's menu staying open to the previous tab).

I am sure I am deleting player informations in my Menu. I wasn't for quite a time but the latest version should be doing it. I will recheck and post on the Menus topic

Well, I investigated a bit further... opened up a few windows, extended the challenge widget, and opened the menu; quit the server, then rejoined. I could of sworn the challenge widget exhibited the same behavior, but it seems only the Menu plugin...

But alas, it's my own fault... I'm still using v1.62, and I see the issue was fixed in v1.64. I had just assumed the removeplayerdata function handled all that, and didn't quite feel up to hacking up the menu again to just how I ike it.

At the moment i have got some of the files of the old public DB as shown on the sourceforge page....

Why i got these files you might ask?

Well as an relief for the database of dedimania i thought lets make the public db of aseco relive again.

The only problem im having problems with are with the quotedstring in the plugin.

Thats why im asking some people to bug test it with me or that want to help.

PM me or send an email if you want to help.

For AM:

Do you still have the aseco_server.php file as i cant find it on the web. Or know of any solutions.

With kind regards.

There never was an "aseco_server.php" file. The public database functions were completely contained within the database itself. I might be able to dig up a version of the function defs if you want, and maybe the files for granting access too.

Basically the MySQL database has to be publicly accessible. You grant a user access to the functions/procedures, then the aseco php files connect to the DB and do all the database stuff through db functions.

Keep in mind the original purpose of the public db... It's intended as a global records system to take the place of the localdb (same purpose DM has for FAST), whereas Dedimania in Aseco/Xaseco is intended primarily as a leaderboard. They are meant to be interoperable, not interchangeable.

nocturne wrote:Keep in mind the original purpose of the public db... It's intended as a global records system to take the place of the localdb (same purpose DM has for FAST), whereas Dedimania in Aseco/Xaseco is intended primarily as a leaderboard. They are meant to be interoperable, not interchangeable.

Actually the public DB was designed to function WITH the local database. It wasn't supposed to be a complete replacement for the local database.

Local DB is pretty much required for ASECO now anyway, it's too crippled without it.

Bug when someone write a wrong command for example my login is test12 if i wrote /admin kick or /admin kick test11 its a wrong command name and we have the sendservermessage >> Admin kicked player " " ...... This message must sended only if the command params or login is correct.This bug works on all aseco versions

This was mentioned in another thread recently. Again, I don't think of it really as a bug... just a different way of thinking. Besides, the playerlist check was in the original Aseco v.61 -- so not including it in v2.x just seems intentional (for usage to clear out 'bugged' disconnects and 'ghost' players I suppose, instead of a redundant 'kickghost' command like Xaseco).

Also, it can be fun to mess around with, using a nickname instead of the login..