To add to Colons post, the web admin (BFAdminCP) will have its update in a few weeks, 3 to 4 weeks max. After this update any future updates (new features), besides bugfixes, won't happen as well. I'll be doing another project and will require all most focus.

- Every time I allow/disallow a command for a usergroup, the config line selection jumps to the top.
- [AdKats] ERROR: Error in record information, unable to log procon event.
Cause for the second error?

- Every time I allow/disallow a command for a usergroup, the config line selection jumps to the top.
- [AdKats] ERROR: Error in record information, unable to log procon event.
Cause for the second error?

1. It's caused by the setting framework procon uses, I can't avoid it. Every time you make a change that could modify the elements in each of those lists, all of them need to be regenerated.
2. I'll look into that one.

EDIT: I found #2 and fixed it, i'm going to wait to post that update though, in case more are found now that need fixing.

I don't know why my adkats_user table doesn't show the user_expiration and user_notes column? I tried to run the sql file on my bf4 db but still doesn't work. (my bf3's adkats works just fine. Then I tried bf4 but this happens, both are different db)

To add to Colons post, the web admin (BFAdminCP) will have its update in a few weeks, 3 to 4 weeks max. After this update any future updates (new features), besides bugfixes, won't happen as well. I'll be doing another project and will require all most focus.