New Scripting Plan:

Maps -> Database (Script Files) -> Skins,Teams,Coordinates,Weather,Time,Checkpoints,Pickups and Objects \
																										 \
																										  \
Loading/Restarting -> GameMode -> Loading Database (Script Files) -> Restarts Each Time -------------------|
																										  /
																										 /
Everything else FilterScript -> Loads The Maps ----------------------------------------------------------
	   /
	  |
	  |
	  |
	  |
	  |
The Cycle Control
The IRC System
The Mission System
User Account System/Per Mission Data
Textdraws

<------->

Advantages of this way;
1) Multiple scripters can work on the script; without worries.
2) The Mission adding could be done from a web, i.e very easy someone without script knowlodge can do it. Make it scripter only. (Will explain you the reason)

Dis-advantage:
1)This can limit us what we can do to a script.
2)Maps from database can't have some speical info's that we can only store in/or Per map script / message.

<----->


And The Best one i could think of took me whole night to do it;

FilterScript -> Maps -> Skins,Teams,Coordinates,Weather,Time,Checkpoints,Pickups and Objects \
																							  \
Everything else GameMode -> Loads The Maps ---------------------------------------------------/
	   /
	  |
	  |
	  |
	  |
	  |
The Cycle Control
The IRC System
The Mission System
User Account System/Per Mission Data
Textdraws


Advantages:
1) No Server restart. After really long searching on forums and asking, got to know this is not a problem better say more stable thing. As sending class selection is client side.
2) Maps can be added by the scripters very easily but this way they can change cycle and make it how they want it to be.
3) No limits with the script.
4) Better control of cycle, easy changing an more that no one else can add missions expect the scripting team. CAN explain why too.

Dis-advantage:
1) We might have to use 'y_classes.inc' for it.

As server won't restart the old player class won't be deleted, and player will see it each time he selects class. By y_classes we can disable it delete it enable it all we want.


Note: Saying system in both should be MySQL.