[MaKTaiL]

Originally Posted by FeuerSturm I won't be home at the weekend, so I just have about an hour today and a few hours tomorrow after work. I'll see what I can do, no promises though!

Thank you so much!

[Mosalar]

[Request]

Would it be possible to make this aio modular(like Olly did with is irc relay)? The main reason many use sm over mani is the way we can config it. Instead of disabling some cvars, we just don't add that plugin. Also I know your reputation from the amxx days, you won't stop until you have created the ultimate.... :-)

Most of us will be able to strip the unneeded code, but some will get all ffed up trying to set all the cvars.

And again, thank you for the specialized dods coding, we've needed it for sometime..

[Beleriand]

Hi,

you could fix it so fast, great!

I knew how to swapteams only on jagd and strand, but thanks for describing it again for other users.

This is a fantastic plugin!

+karma4Feuersturm

[FeuerSturm]

Originally Posted by Mosalar [Request] Would it be possible to make this aio modular(like Olly did with is irc relay)? The main reason many use sm over mani is the way we can config it. Instead of disabling some cvars, we just don't add that plugin. Also I know your reputation from the amxx days, you won't stop until you have created the ultimate.... :-) Most of us will be able to strip the unneeded code, but some will get all ffed up trying to set all the cvars. And again, thank you for the specialized dods coding, we've needed it for sometime..

I already thought about adding the features as addons to the base plugin,
but the problem is that the features are almost all independent, so there's
nothing I could use from the base, so each addon would be an independent plugin.
If i release all features as independent plugins, there's nothing DoD specific (besides thet class management & swapteams) anymore
and then almost all of the plugins have already been made, working or not

What I thought of next was make the features "definable" in the source,
so you can "unuse" the code by commenting out the "#define", would
be less work for modders than removing all code for unneeded features.

Any thoughts on that?

[dirtyjob]

thnx on the auto assign fix

[Lebson506th]

Originally Posted by FeuerSturm What I thought of next was make the features "definable" in the source, so you can "unuse" the code by commenting out the "#define", would be less work for modders than removing all code for unneeded features. Any thoughts on that?

Or you could make a cvar to enable or disable each part so users didn't have to recompile it to change things.

[MaKTaiL]

I was looking at all the commands you did for this plugin and I founded some:

[001] cls_30cal - No description available
[002] cls_bar - No description available
[003] cls_bazooka - No description available
[004] cls_garand - No description available
[005] cls_k98 - No description available
[006] cls_k98s - No description available
[007] cls_mg42 - No description available
[008] cls_mp40 - No description available
[009] cls_mp44 - No description available
[010] cls_pschreck - No description available
[011] cls_spring - No description available
[012] cls_tommy - No description available

I try to type one of them in the console and I got this error:

L 08/28/2008 - 0865: [SM] Native "GetClientTeam" reported: Client index 0 is invalid
L 08/28/2008 - 0865: [SM] Displaying call stack trace for plugin "dod_teammanager_source.smx":
L 08/28/2008 - 0865: [SM] [0] Line 511, dod_teammanager_source.sp::cmd_ClassSelect()

Is it something that we have to worry about?

[Lebson506th]

Thanks because those are class switch commands for admin.

They allow an admin playing switch to any class they want bypassing restrictions.

The reason that error is coming up is because you are using it via RCON or the HLSW console which is client # 0.

[MaKTaiL]

Originally Posted by Lebson506th Thanks because those are class switch commands for admin. They allow an admin playing switch to any class they want bypassing restrictions. The reason that error is coming up is because you are using it via RCON or the HLSW console which is client # 0.

Ohh, now I got it. Thank you for the information.

[FeuerSturm]

Originally Posted by Lebson506th Or you could make a cvar to enable or disable each part so users didn't have to recompile it to change things.

All features already have cvars to enable/disable, the request was rather to split the plugin in a base and addons so that people don't need
to load the code for features they don't want to use at all.

Even though the performance difference would be not even noticable,
I can understand that.

Originally Posted by Lebson506th Thanks because those are class switch commands for admin. They allow an admin playing switch to any class they want bypassing restrictions. The reason that error is coming up is because you are using it via RCON or the HLSW console which is client # 0.

Semi-correct, those "cls_*" commands are the standard dod commands to
select your playerclass, if you chose the class "Allied Rifleman" in the menu, you automatically execute the command "cls_garand", no
matter if the plugin is running or not.
I'm just hooking those commands to "open" the class if an admin wants to join a full one, or if a player wants to select a class that is restricted
by a "blocked until X players rule".