[Hawk552]

Originally Posted by v3x You should use either Vault, nVault, or Array to store the ids ;)

Vault is slower, and Array is overkill.

[Janet Jackson]

The advantage of an .ini file is that it's easily exchangeable with other servers. Or can this also be done when it's using one of the other methods ?

[Hawk552]

Originally Posted by Janet Jackson The advantage of an .ini file is that it's easily exchangeable with other servers. Or can this also be done when it's using one of the other methods ?

With array it's possible, but array is still overkill.

For vault, you would need to find each and every key related to this, and then cut them out.

[SubStream]

anyhow Sean good job on getting it done so quickly... Nice work

[Sean D]

version 0.2

- fixed the amx_ban and amx_addban
- added amx_log stuff


that's all i wanted to add to/fix with it, if you want it to print that a flag has been added based on amx_show_activity i'll do it, but i don't see the point, because flagging is more of a behind-the-scenes plugin.... whatever

[Charming]

Originally Posted by v3x You should use either Vault, nVault, or Array to store the ids ;)

sorry hawk i gotta agree with v3x.

[Hawk552]

Originally Posted by Charming Originally Posted by v3x You should use either Vault, nVault, or Array to store the ids ;) sorry hawk i gotta agree with v3x.

Why? A file is much better for this purpose. Tell me one reason vault is better.

[Janet Jackson]

Originally Posted by Sean D - there are two files created in your configs directory: flagging.ini and flagcmds.ini - this stores the stuff you use or whatever

flagcmds.ini was created, flagging.ini (or anything similar) wasn't.

[Sean D]

sorry about that.. and thanks for trying it out

it won't create flagging.ini until you add a flag to it, and flagcmds.ini is created because the two commands default and bandefault are needed within the plugin (if you delete them, you won't add a flag when you try to do amx_flags add <player> or amx_ban/amx_addban)

also, if you delete all of the commands in flagcmds.ini, it will just create a new file with default/bandefault back in there, so you don't have to go to the file and delete it yourself or whatever (same with flagging.ini, only nothing new is created)

thanks again janet

[Janet Jackson]

Originally Posted by Sean D it won't create flagging.ini until you add a flag to it

I added two or three by typing

amx_flags add "STEAM_x:x:xxxxx"

The players were found and the flags were added according to the messages that were returned in my console. I checked immediately if flagging.ini was created, but it wasn't. I checked again after a mapchange, but there was still no flagging.ini.