Looking at your code, if you plan to have multiple people working on this, you should better organize how commands are processed.
To make things easier, everyone should create their own functions/subs, and nobody should be forced to edit the "main", built in subs.
For example, command processing, I would do like this..
[div class='codetop']CODE[/div][div class='codemain' style='height:200px;white-space:pre;overflow:auto']'// Access Requirements
PNF_Lockdown_CMD_Access = 90
Sub PNF_Commands(Username, Flags, Message, Ping, From)
Select Case LCase(Message)
Case "?lockdown": PNF_Lockdown_CMD Username, Message, From
End Select
End Sub
Sub PNF_Lockdown_CMD(Username, From)
GetDBEntry Username, uAccess, uFlags
If uAccess < PNF_Lockdown_CMD_Access Then
Exit Sub
End If
If InStr(Message, " ") > 0 Then
Arg = Split(Message, " ", 2)(1)
Select Case LCase(Arg)
Case "on": SetSetting "PNF", "Lockdown", True, "", True
DSP From, "[PNF] Lockdown Enabled", Username, vbGreen
Case "off": SetSetting "PNF", "Lockdown", False, "", True
DSP From, "[PNF] Lockdown Disabled", Username, vbRed
End Select
Else
If GetSetting("PNF", "Lockdown") Then
DSP From, "[PNF] Lockdown is active.", Username, vbGreen
Else
DSP From, "[PNF] Lockdown is disbabled.", Username, vbRed
End If
End If
End Sub
Sub PNF_Event_UserTalk(Username, Flags, Message, Ping)
PNF_Commands Username, Flags, Message, Ping, 3
End Sub[/div]
This makes it VERY easy to add a new command. A person writes their sub routine, and creates a simple call to their sub routine within the commands main routine.
This isolates all code created by everyone, so errors can easily be found. If a single sub routine is having problems, that sub routine can be disabled.
