[wEight]

First, i know there is an option (cvar) to do it instead of just writing debug in every line. I'm just curious, would it cause problems?

[wickedd]

Why would you want to do that?

P.S. It's recommended that you do not add debug after every plugin.

[fysiks]

There's a cvar to debug all plugins????? I don't think there is. Putting a plugin into debug mode has to happen prior to the plugin being loaded AFAIK.

Anyways, you should only use debug on plugins from which you are getting errors.

[Kia]

Originally Posted by wEight First, i know there is an option (cvar) to do it

Tell me more.

[wEight]

// Plugin Debug mode
// 0 - No debugging (garbage line numbers)
// 1 - Plugins with "debug" option in plugins.ini are put into debug mode
// 2 - All plugins are put in debug mode
// Note - debug mode will affect JIT performance
//
// Default value: 1
amx_debug 1

Not sure if cvar, it is located in amxx.cfg so that got me confused.

@wickedd I was just curious, not recommended is enough..so thanks
@fysiks, amx_debug....Idk i downloaded my dedicated server from the net..
And one time my server crashed console gave me an error of a plugin my server used for like more than 2 weeks and it didn't compile with any errors (If that has to do with anything). Then after 2 more weeks the console reported the same plugin (This time it was in debug mode) Does this have to do with another plugin or something else?

[fysiks]

Well, I feel kinda dumb lol. It must be in the core of AMX Mod X because I didn't see it in any plugin.

Putting a plugin in debug mode won't fix anything.

If a plugin compiles without errors, that doesn't mean it won't have run-time errors.
When you see an error from a plugin and it's not already in debug mode, you need to put it into debug mode and wait until the error happens again. When the error does happen again, you will get a more detailed output for that error in the error logs. When you get this, you need to post the whole error outputs in a new post in the plugin's own thread.

[fysiks]

Originally Posted by WildCard65 You do realize that AMXX can create cvars without the help of a plugin cause it has access to the hl code, it's also how it exposes that to plugins.

LOL. I'm not dumb. Hence why I said "it's probably in the core of AMX Mod X".

[WildCard65]

Originally Posted by fysiks LOL. I'm not dumb. Hence why I said "it's probably in the core of AMX Mod X".

Just making sure. I'm only human

[wEight]

Originally Posted by fysiks Well, I feel kinda dumb lol. It must be in the core of AMX Mod X because I didn't see it in any plugin. Putting a plugin in debug mode won't fix anything. If a plugin compiles without errors, that doesn't mean it won't have run-time errors. When you see an error from a plugin and it's not already in debug mode, you need to put it into debug mode and wait until the error happens again. When the error does happen again, you will get a more detailed output for that error in the error logs. When you get this, you need to post the whole error outputs in a new post in the plugin's own thread.

Alright, so error logs... got it

And you mean it is hard-coded into amxmodx?

[fysiks]

Originally Posted by wEight And you mean it is hard-coded into amxmodx?

It's irrelevant where the cvar is located. Simply do as I suggested.