ItsMods

I dunno what's causing the problem. Maybe it's because of linux but I can't try that out (and it still seems unlikely!). Just triple check if you didn't do anything wrong, lol.

(01-14-2012, 14:07)Pozzuh Wrote: [ -> ]I dunno what's causing the problem. Maybe it's because of linux but I can't try that out (and it still seems unlikely!). Just triple check if you didn't do anything wrong, lol.

I reinstalled the addon, added permissions plugin, added warn plugin.
added the configuration of permissions to sv_config.ini and didn't change anything.

i can still warn myself......

i doubt it has anything to do with my configuration.

i do get errors in the terminal: Failed to parse "addon", "MW3_warn","_PermissionPlugin"

Don't know if this is an error that can be fixed

hmm, that seems to be something not working correctly in the addon it self. I'll have to ask @Nukem

---

Nukem will look into it..

Hey,

As i'm currently developing a plugin myself (with temporary permissions for Snowy Leopard until you or Nukem can pinpoint the problem) I just looked over your code and was wondering:
Your plugin essentially relies on being the first plugin to get the chat fed right? so if another plugins gets it first, yours can't do anything about it, or am i mistaking?

Your code looks a lot better formatted than mine btw
-Bonemind

Edit: Typo

(01-16-2012, 01:26)bonemind Wrote: [ -> ]Hey,

As i'm currently developing a plugin myself (with temporary permissions for Snowy Leopard until you or Nukem can pinpoint the problem) I just looked over your code and was wondering:
Your plugin essentially relies on being the first plugin to get the chat fed right? so if another plugins gets it first, yours can't do anything about it, or am i mistaking?

Your code looks a lot better formatted than mine btw
-Bonemind

Edit: Typo

You're right. But since my plugin is called 'aaaPermissionPlugin' I don't worry..

(01-16-2012, 01:26)bonemind Wrote: [ -> ]Hey,

As i'm currently developing a plugin myself (with temporary permissions for Snowy Leopard until you or Nukem can pinpoint the problem) I just looked over your code and was wondering:
Your plugin essentially relies on being the first plugin to get the chat fed right? so if another plugins gets it first, yours can't do anything about it, or am i mistaking?

Your code looks a lot better formatted than mine btw
-Bonemind

Edit: Typo

You are correct. That's why you shouldn't rename the plugin.


Omg @Pozzuh ninja

Ok, thanks guys

@Pozzuh would you mind adding some sort of "immunity" function into your permission plugin?
because up to now for example: a admin could ban a other admin just because he has permission to run the command. I don't think thats good ^^

I hope you agree

(01-17-2012, 20:42)Deviler86 Wrote: [ -> ]@Pozzuh would you mind adding some sort of "immunity" function into your permission plugin?
because up to now for example: a admin could ban a other admin just because he has permission to run the command. I don't think thats good ^^

I hope you agree

It would be impractical. There is no !ban in my plugin. Not going to do that, I'm sorry.

(01-17-2012, 20:54)Pozzuh Wrote: [ -> ]

(01-17-2012, 20:42)Deviler86 Wrote: [ -> ]@Pozzuh would you mind adding some sort of "immunity" function into your permission plugin?
because up to now for example: a admin could ban a other admin just because he has permission to run the command. I don't think thats good ^^

I hope you agree

It would be impractical. There is no !ban in my plugin. Not going to do that, I'm sorry.

it was just an example.. but nvm, of course you can't check something like that if your plugin doesn't know what the command does ^^
my fault ^^