View Full Version : Best Admin Tool?
KCGThanatos
01-12-2004, 02:18 PM
As I am not up for giving out the rcon password to multiple admins in my server, I would like to know what would be the best admin tool for assigning individual admins individual rights... kinda like tha admin mod that was out for Counter-Strike when you could assign different levels of admin access per user. It also needs to be accessible while in game and not have to exit to kick someone.
Thanks
imported_Eroc
01-12-2004, 02:52 PM
(if your using Linux) UDPB-COD by far !
It has 5 levels of admins, broadcasting messages, funnies, banning, kicking, ping detection, pretty much everything needed to administer the server.
You can check it out at www.udpviper.com or visit our servers at 69.44.153.157:28960/70/80/90 with it.
Eroc
KCGThanatos
01-12-2004, 04:09 PM
Windows 2k3
wowdisturbed
01-13-2004, 09:19 AM
We have a new Admin tool out for Call of Duty. You should give it a test drive. you can get this from here codadmin.com under downloads or you can get it from our website as well at wizardsofwar.com . Well give us some feed back on this. We have been using this for about 2 months now we just released it to the public 2 days ago. Well I think this is ranked up there in the top 5 admin tool that I have used. Very low CPU usage. And that is a big thing to me. I am sure it is to you as well. Thanks for you input and time.
=WoW= Disturbed
KCGThanatos
01-13-2004, 10:13 AM
I tried it and everytime I get this:
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.ArgumentException: Invalid value 0 for parameter interval.
at System.Timers.Timer..ctor(Double interval)
at GameServerAdmin.MainForm.btnStartStop_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventAr gs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.ControlNativeWindow.OnMessage (Message& m)
at System.Windows.Forms.ControlNativeWindow.WndProc(M essage& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
************** Loaded Assemblies **************
mscorlib
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.573
CodeBase: file:///c:/windows/microsoft.net/framework/v1.1.4322/mscorlib.dll
----------------------------------------
GameServerAdmin
Assembly Version: 1.0.1468.41309
Win32 Version: 1.0.1468.41309
CodeBase: file:///D:/GSA/GameServerAdmin.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.573
CodeBase: file:///c:/windows/assembly/gac/system.windows.forms/1.0.5000.0__b77a5c561934e089/system.windows.forms.dll
----------------------------------------
System
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.573
CodeBase: file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
----------------------------------------
System.Drawing
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.573
CodeBase: file:///c:/windows/assembly/gac/system.drawing/1.0.5000.0__b03f5f7f11d50a3a/system.drawing.dll
----------------------------------------
System.Data
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.573
CodeBase: file:///c:/windows/assembly/gac/system.data/1.0.5000.0__b77a5c561934e089/system.data.dll
----------------------------------------
System.Xml
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.573
CodeBase: file:///c:/windows/assembly/gac/system.xml/1.0.5000.0__b77a5c561934e089/system.xml.dll
----------------------------------------
************** JIT Debugging **************
To enable just in time (JIT) debugging, the config file for this
application or machine (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.
For example:
<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>
When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the machine
rather than being handled by this dialog.
vBulletin® v3.8.7, Copyright ©2000-2012, vBulletin Solutions, Inc.