Eventscript flooding my console with 'couldnt exec' ...

maitredede · **Author**

Hi

First, Great plugin, I love it. It make fun and admin more powerfull

But...

My console is flooded with each scripts the plugin tries to fire, and then fire it...
For example, I have cfg/noautosnipe/player_hurt.cfg

I do a :

Code:

mattie_eventscripts 1
eventscripts_register noautosnipe

And the console is flooded with :

Code:

couldn't exec \player_hurt.cfg

Here is my file :

Code:

//es_msg #green event_var(weapon)
if(event_var(weapon) equalto "sg550") then ma_cexec es_steamid drop

ajax · 05-31-2005 , 15:02

create an empty file here... cfg/player_hurt.cfg

maitredede · 05-31-2005 , 16:26

Ok, but that means that I will fill my cfg dir with empty scripts...

ajax · 05-31-2005 , 17:22

Quote:

Originally Posted by maitredede

Ok, but that means that I will fill my cfg dir with empty scripts...

right now that is the only solution... either console spam or empty files. you get to choose.

i think Mattie is working on a solution, but it's a valve message.

Cr3V3TT3 · 05-31-2005 , 22:38

:/

thats could not be possible i think
because the plugin is checking for the file before executing it

Code:

      if(filesystem->FileExists(szCommand))

maitredede · 06-01-2005 , 03:55

Ok

So does it means that the plugin will execute all scripts for an event, that are in the registred packs ? for example, in the pack 'p1' there is a script player_hurt.cfg and in the root dir another player_hurt.cfg. Will both be executed ?

Mattie · 06-01-2005 , 08:34

Quote:

Originally Posted by maitredede

Ok

So does it means that the plugin will execute all scripts for an event, that are in the registred packs ? for example, in the pack 'p1' there is a script player_hurt.cfg and in the root dir another player_hurt.cfg. Will both be executed ?

Yes, both will be executed. (All scripts in the root event dir will be executed, no matter what script packs you have installed.)

If a script pack contains a .cfg file, ES will automatically try to run a copy of that event .cfg from your ES root directory. That's the message you're seeing. Just create an empty one to bypass the message.

maitredede · 06-01-2005 , 09:10

Ok, thanks.

Mattie, If I could, I would give you a big kiss for that plugin...