Ok, there were several misunderstandings here. Let me correct my mistakes. In fact I did not know I had to compile the plugins for adminmod. When I first read adminmod's documentation (this one is excellent) I got to the point of "there are 150+ pluggins to download" and was happy with that info, and can't remember reading that pluggins were or were not ready to use. (They are not, of course).
I did not go any farther on the reading because I was under the impression they would be distributed ready to be added to the dll directory or something (actually, after succesfull compilation they are amx files going to the scripts directory). This is MY mistake, and I apologize for that. The poor documentation I was referring to was admin_listen's; I was at least expecting a small note on the readme file pointing out to "compile as required by adminmod in XXXXXXXX.html" or so. (I usually do that when I write documentations). But, at this point we find out that we were talking about different things and all the discussion becomes meaningless ! Thank you for your patience and time. At 12:31 AM 12/18/2002, you wrote:
http://www.adminmod.org/help/online/ A help file is also distributed with the download (in the docs/ directory) in PDF format I believe. Go to the index and type: "compile" and it has a list of entries to look at. The best one for you would be: http://www.adminmod.org/help/online/Scripting_Basics/Compiling_Admin_Mod_Scr ipts_101.htm If it mentions <x>.bat just ignore the .bat extension for linux... Was the manual that hard to find? (seriously, I thought it was obvious, but is it not mentioned in the readme???) Alfred
_______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
