Advanced In-Game Admin and Ban Enforcer - AdKats

[ImportBot]

Originally Posted by PotatoKiller*:

 

he says he cant,because it was anticheat ban,not from admins... that is the problem

[ColColonCleaner]

Originally Posted by ColColonCleaner*:

 

he says he cant,because it was anticheat ban,not from admins... that is the problem

A DPS live ban is from the AdKats plugin. This is not a global ban, and only exists on Timm's server. A simple unban for your player is all that is needed. Unless you mean Timm trusts the anti-cheat script I wrote without question. It is a very good script, but there are still ways battlelog can make it issue false bans, and this appears to be one of them.

[ImportBot]

Originally Posted by PotatoKiller*:

 

ok) thx again)

[ImportBot]

Originally Posted by EntraVenuS*:

 

Hi

i seem to be getting this error and i cannot for the life of me find out why its happening (also im hoping this is related to the fact of my stats page not working as intended to )

(the ***** is my database name taken out for obvious reasons )

Thanks in advance

 

[07:05:44 74] [AdKats] INSERT INTO `******_db2`.`adkats_settings`

(

`server_id`,

`setting_name`,

`setting_type`,

`setting_value`

)

VALUES

(

4,

Metabans Username,

multiline,

 

)

ON DUPLICATE KEY

UPDATE

`setting_value` =

[ColColonCleaner]

Originally Posted by ColColonCleaner*:

 

Hi

i seem to be getting this error and i cannot for the life of me find out why its happening (also im hoping this is related to the fact of my stats page not working as intended to )

(the ***** is my database name taken out for obvious reasons )

Thanks in advance

 

[07:05:44 74] [AdKats] INSERT INTO `******_db2`.`adkats_settings`

(

`server_id`,

`setting_name`,

`setting_type`,

`setting_value`

)

VALUES

(

4,

Metabans Username,

multiline,

 

)

ON DUPLICATE KEY

UPDATE

`setting_value` =

What is the error next to this one in the logs? I need the actual error message. This log line just shows which query caused the error.

[ImportBot]

Originally Posted by )RAG()N*:

 

is there a way to stop this adkats mass messages ?

 

 

[ColColonCleaner]

Originally Posted by ColColonCleaner*:

 

is there a way to stop this adkats mass messages ?

 

 

Update to 6.9.0.10, that should fix the issue.

[ImportBot]

Originally Posted by EntraVenuS*:

 

got the rest of it

 

18:16:27 79] [AdKats] INSERT INTO `******_db2`.`adkats_settings`

(

`server_id`,

`setting_name`,

`setting_type`,

`setting_value`

)

VALUES

(

4,

Teamspeak Secondary Channel Names,

multiline,

Team+1|Team+2

)

ON DUPLICATE KEY

UPDATE

`setting_value` = Team+1|Team+2

[18:16:27 79] [AdKats] INSERT INTO `******_db2`.`adkats_settings`

(

`server_id`,

`setting_name`,

`setting_type`,

`setting_value`

)

VALUES

(

4,

Teamspeak Secondary Channel Names,

multiline,

Team+1|Team+2

)

ON DUPLICATE KEY

UPDATE

`setting_value` = Team+1|Team+2

[ImportBot]

Originally Posted by keb2*:

 

When AdCats is enabled for a long time, an error occurs

????????:

Stopped working

 

????????? ????????:

??? ??????? ????????: CLR20r3

????????? ???????? 01: procon.exe

????????? ???????? 02: 1.5.1.1

????????? ???????? 03: 55083e97

????????? ???????? 04: System.Core

????????? ???????? 05: 3.5.0.0

????????? ???????? 06: 4ca2d78d

????????? ???????? 07: 586

????????? ???????? 08: 53

????????? ???????? 09: System.InvalidOperationException

?????? ??: 6.1.7601.2.1.0.1296.17

??? ?????: 1049

 

???????????? ? ?????????? ? ?????????????????? ? ?????????:

http://go.microsoft.com/fwlink/_link...8&clcid=0x0419

 

???? ????????? ? ?????????????????? ? ????????? ??????????, ???????????? ? ??? ????????? ?????????:

C:\Windows\system32\ru-RU\erofflps.txt

 

But at the same time procon and all its plugins work with some lag.If you disable Adkats then the error does not appear.

How to solve this problem?

[ImportBot]

Originally Posted by )RAG()N*:

 

Update to 6.9.0.10, that should fix the issue.

But I have 6.9.0.11

[ColColonCleaner]

Originally Posted by ColColonCleaner*:

 

But I have 6.9.0.11

Then the automatic updater already took the patch and you should no longer see the problem. Cheers.

[ColColonCleaner]

Originally Posted by ColColonCleaner*:

 

When AdCats is enabled for a long time, an error occurs

????????:

Stopped working

 

????????? ????????:

??? ??????? ????????: CLR20r3

????????? ???????? 01: procon.exe

????????? ???????? 02: 1.5.1.1

????????? ???????? 03: 55083e97

????????? ???????? 04: System.Core

????????? ???????? 05: 3.5.0.0

????????? ???????? 06: 4ca2d78d

????????? ???????? 07: 586

????????? ???????? 08: 53

????????? ???????? 09: System.InvalidOperationException

?????? ??: 6.1.7601.2.1.0.1296.17

??? ?????: 1049

 

???????????? ? ?????????? ? ?????????????????? ? ?????????:

http://go.microsoft.com/fwlink/_link...8&clcid=0x0419

 

???? ????????? ? ?????????????????? ? ????????? ??????????, ???????????? ? ??? ????????? ?????????:

C:\Windows\system32\ru-RU\erofflps.txt

 

But at the same time procon and all its plugins work with some lag.If you disable Adkats then the error does not appear.

How to solve this problem?

I have no idea what could cause that. It hasn't been reported before, and that crash report doesn't give me much information. How long after you start procon does it crash?

[ColColonCleaner]

Originally Posted by ColColonCleaner*:

 

got the rest of it

 

18:16:27 79] [AdKats] INSERT INTO `******_db2`.`adkats_settings`

(

`server_id`,

`setting_name`,

`setting_type`,

`setting_value`

)

VALUES

(

4,

Teamspeak Secondary Channel Names,

multiline,

Team+1|Team+2

)

ON DUPLICATE KEY

UPDATE

`setting_value` = Team+1|Team+2

[18:16:27 79] [AdKats] INSERT INTO `******_db2`.`adkats_settings`

(

`server_id`,

`setting_name`,

`setting_type`,

`setting_value`

)

VALUES

(

4,

Teamspeak Secondary Channel Names,

multiline,

Team+1|Team+2

)

ON DUPLICATE KEY

UPDATE

`setting_value` = Team+1|Team+2

All of your errors are coming from attempts to write to the settings table. Did something happen to your database recently? Run the following query on your database and tell me what it says:

 

INSERT INTO `adkats_settings`

(

`server_id`,

`setting_name`,

`setting_type`,

`setting_value`

)

VALUES

(

4,

"Teamspeak Secondary Channel Names",

"multiline",

"Team+1|Team+2"

)

ON DUPLICATE KEY

UPDATE

`setting_value` = "Team+1|Team+2"

[ColColonCleaner]

Originally Posted by ColColonCleaner*:

 

Code:

[14:52:15 21] [AdKats] EXCEPTION-6900-RunAction-ActionHandling38: [Command Previous Temp Ban not found in runAction. Record ID 446887]
[14:52:26 06] [AdKats] EXCEPTION-6900-RunAction-ActionHandling38: [Command Previous Temp Ban not found in runAction. Record ID 446887]
[14:52:32 58] [AdKats] User List Fetched from Database. [140 users, 5 Special Players, 292 Fetched Players]
[14:52:38 20] [AdKats] SQL updates fetched from backup location.
[14:52:42 08] [AdKats] EXCEPTION-6900-RunAction-ActionHandling38: [Command Previous Temp Ban not found in runAction. Record ID 446887]
[14:52:53 22] [AdKats] EXCEPTION-6900-RunAction-ActionHandling38: [Command Previous Temp Ban not found in runAction. Record ID 446887]
[14:53:04 79] [AdKats] EXCEPTION-6900-RunAction-ActionHandling38: [Command Previous Temp Ban not found in runAction. Record ID 446887]
[14:53:15 72] [AdKats] EXCEPTION-6900-RunAction-ActionHandling38: [Command Previous Temp Ban not found in runAction. Record ID 446887]
[14:53:26 59] [AdKats] EXCEPTION-6900-RunAction-ActionHandling38: [Command Previous Temp Ban not found in runAction. Record ID 446887]
[14:53:37 35] [AdKats] EXCEPTION-6900-RunAction-ActionHandling38: [Command Previous Temp Ban not found in runAction. Record ID 446887]
[14:53:48 55] [AdKats] EXCEPTION-6900-RunAction-ActionHandling38: [Command Previous Temp Ban not found in runAction. Record ID 446887]
[14:53:59 50] [AdKats] EXCEPTION-6900-RunAction-ActionHandling38: [Command Previous Temp Ban not found in runAction. Record ID 446887]
[14:54:10 44] [AdKats] EXCEPTION-6900-RunAction-ActionHandling38: [Command Previous Temp Ban not found in runAction. Record ID 446887]
[14:54:21 53] [AdKats] EXCEPTION-6900-RunAction-ActionHandling38: [Command Previous Temp Ban not found in runAction. Record ID 446887]
[14:54:32 32] [AdKats] EXCEPTION-6900-RunAction-ActionHandling38: [Command Previous Temp Ban not found in runAction. Record ID 446887]
[14:54:43 29] [AdKats] EXCEPTION-6900-RunAction-ActionHandling38: [Command Previous Temp Ban not found in runAction. Record ID 446887]
[14:54:54 18] [AdKats] EXCEPTION-6900-RunAction-ActionHandling38: [Command Previous Temp Ban not found in runAction. Record ID 446887]
[14:55:05 19] [AdKats] EXCEPTION-6900-RunAction-ActionHandling38: [Command Previous Temp Ban not found in runAction. Record ID 446887]
[14:55:16 01] [AdKats] EXCEPTION-6900-RunAction-ActionHandling38: [Command Previous Temp Ban not found in runAction. Record ID 446887]
[14:55:27 04] [AdKats] EXCEPTION-6900-RunAction-ActionHandling38: [Command Previous Temp Ban not found in runAction. Record ID 446887]
[14:55:38 27] [AdKats] EXCEPTION-6900-RunAction-ActionHandling38: [Command Previous Temp Ban not found in runAction. Record ID 446887]
[14:55:49 71] [AdKats] EXCEPTION-6900-RunAction-ActionHandling38: [Command Previous Temp Ban not found in runAction. Record ID 446887]
[14:56:01 22] [AdKats] EXCEPTION-6900-RunAction-ActionHandling38: [Command Previous Temp Ban not found in runAction. Record ID 446887]

What is it and what threatens?

Note to self, block this from happening.

[ImportBot]

Originally Posted by EntraVenuS*:

 

All of your errors are coming from attempts to write to the settings table. Did something happen to your database recently? Run the following query on your database and tell me what it says:

 

INSERT INTO `adkats_settings`

(

`server_id`,

`setting_name`,

`setting_type`,

`setting_value`

)

VALUES

(

4,

"Teamspeak Secondary Channel Names",

"multiline",

"Team+1|Team+2"

)

ON DUPLICATE KEY

UPDATE

`setting_value` = "Team+1|Team+2"

It actually went in thanks for that

 

Plus while im here i would like to empty the whole database but .. keep all the settings, I.E admins and all settings i have used on adkats.

What would i need to back up so i can basically start afresh but with the old settings and admins

 

Thanks in advance

[ColColonCleaner]

Originally Posted by ColColonCleaner*:

 

It actually went in thanks for that

 

Plus while im here i would like to empty the whole database but .. keep all the settings, I.E admins and all settings i have used on adkats.

What would i need to back up so i can basically start afresh but with the old settings and admins

 

Thanks in advance

If you start again all of the player IDs will be different, so the user soldiers table will be completely invalid. You can import all the users and settings over to the new instance from those tables, adkats_users and adkats_settings, but you'll need to manually assign them their soldiers back once they are given new IDs in the new database by stat logger. In short you'll need to back up the data from the following tables, and import them over your fresh install after running the adkats.sql script on it.

 

adkats_roles, adkats_rolecommands, adkats_settings, adkats_users, adkats_rolegroups

 

You'll probably need to disable foreign key checks while you do the import as some things will be out of order.

[ColColonCleaner]

Originally Posted by ColColonCleaner*:

 

I've had some spare time at home recently to jump back on some things for the AdKats project. I've been working on making hardcoded sections of the plugin available in settings or for experimental usage, and fixing issues where i knew they existed before or people logged issues about them.

 

These are in no particular order.

 

 

• I've added a setting for the minimum minutes into a round before a player can use the assist command, it's in the command settings section.
• I fixed the issue where the error message "cannot find X's persona ID" was spammed in the console and kick log forever.
• I've added settings to the auto-nuke script that allow it to hold a team dead for X seconds instead of just slaying them once.
• I've added settings that can increase the duration of the nuke if a team is so powerful they capture all flags multiple times during a round.
• When auto-nuke duration settings are active, the manual nuke command will also have this duration attached to it.
• For those of you running BF3 and 6.9.0.0 you'll notice the ping enforcer is not functioning, that is fixed in the test builds now.
• I fixed an issue with TeamSwap and the assist command where it would consider a commander to be part of a team's total population and fail to move players over when there was 1 spot open but they had a commander.
• When i left ADK 7 months ago I stopped working on the Top Player Monitor, and at that time the system was in a bad state with quite a few issues. I've begun re-vamping the system into a functional balancer alternative, however, right now only the team power displays are functional. This shows the overall power metrics for each team and also powers the assist command. These metrics will be used for balance later on, but this is currently just a way to make the system visible and functional again. Also all of the performance and loading time issues with the original system have been fixed. This section has been given its own name "Team Power Monitor" and placed in a new setting section, B28.
• I've made the experimental section visible as a setting, however I would not suggest you enable this, it contains a lot of cool features but it also automatically enables a lot of functionality you might not want on your server. Eventually I'm hoping to turn these into settings.
• I've modified the player targeted say/yell/tell messages when issued by an outside script (not an in-game admin) to not trigger the "player has left TEAM (targeted commands)" message. If you issue other commands on them the message will show up but these have been excluded for outside scripts and says issued from procon directly. This is because some people were using ProconRulz to send say messages through AdKats and that caused basically everyone to trigger the player leave message.
• Slight changes to the spambot to make things more reasonable for players, existing code, just moving it public. Players over 75 reputation and players in teamspeak (if you're using the teamspeak integration) are not shown most spambot messages, you can use this as an incentive to help the server. Donation messages are only shown to players who have more than 5 hours play-time in the server, so brand new players don't think you're begging and get angry in chat. Messages about reserved slots are only shown when the server population is high so the message actually means something to people when it's shown. You can bypass this system for specific messages by including [whitelistbypass] including the brackets at the front of that message, then it will be shown to all players, use this for messages about events/giveaways/etc that you want everyone to see.
• Forgives could be issued against people who didn't have infraction points, this has been fixed.
• Added the /ping command, which will display a player's current and average ping in chat. You can just /ping to see your own ping info, or /ping playername to see another player's ping.
• Added the admin /fping command, which will force the layer to ping a player manually instead of trusting the server to ping them, this is more experimental and for giggles than anything else, but sometimes the layer is able to ping a player when their ping is missing.
• Players over 75 reputation now automatically contest reports against them.
• Extended round statistics (tbl_extendedroundstats) older than 60 days are automatically purged for performance reasons.
• Cleaned up some of the messages in the /reportlist command when players were offline.
• Fixed the issue where "command previous temp ban was not found in runaction" was spammed in the console due to an old BFAdminCP issue.
• Fixed issue where the fetch player perks command was marked as an admin command when it shouldn't have been.

This is available on the test branch at the moment, or if you issue a /pupdate.

 

Note to self, line 26890

[Prophet731]

Originally Posted by Prophet731*:

 

I've had some spare time at home recently to jump back on some things for the AdKats project. I've been working on making hardcoded sections of the plugin available in settings or for experimental usage, and fixing issues where i knew they existed before or people logged issues about them.

 

These are in no particular order.

 

 

• I've added a setting for the minimum minutes into a round before a player can use the assist command, it's in the command settings section.
• I fixed the issue where the error message "cannot find X's persona ID" was spammed in the console and kick log forever.
• I've added settings to the auto-nuke script that allow it to hold a team dead for X seconds instead of just slaying them once.
• I've added settings that can increase the duration of the nuke if a team is so powerful they capture all flags multiple times during a round.
• When auto-nuke duration settings are active, the manual nuke command will also have this duration attached to it.
• For those of you running BF3 and 6.9.0.0 you'll notice the ping enforcer is not functioning, that is fixed in the test builds now.
• I fixed an issue with TeamSwap and the assist command where it would consider a commander to be part of a team's total population and fail to move players over when there was 1 spot open but they had a commander.
• When i left ADK 7 months ago I stopped working on the Top Player Monitor, and at that time the system was in a bad state with quite a few issues. I've begun re-vamping the system into a functional balancer alternative, however, right now only the team power displays are functional. This shows the overall power metrics for each team and also powers the assist command. These metrics will be used for balance later on, but this is currently just a way to make the system visible and functional again. Also all of the performance and loading time issues with the original system have been fixed. This section has been given its own name "Team Power Monitor" and placed in a new setting section, B28.
• I've made the experimental section visible as a setting, however I would not suggest you enable this, it contains a lot of cool features but it also automatically enables a lot of functionality you might not want on your server. Eventually I'm hoping to turn these into settings.
• I've modified the player targeted say/yell/tell messages when issued by an outside script (not an in-game admin) to not trigger the "player has left TEAM (targeted commands)" message. If you issue other commands on them the message will show up but these have been excluded for outside scripts and says issued from procon directly. This is because some people were using ProconRulz to send say messages through AdKats and that caused basically everyone to trigger the player leave message.
• Slight changes to the spambot to make things more reasonable for players, existing code, just moving it public. Players over 75 reputation and players in teamspeak (if you're using the teamspeak integration) are not shown most spambot messages, you can use this as an incentive to help the server. Donation messages are only shown to players who have more than 5 hours play-time in the server, so brand new players don't think you're begging and get angry in chat. Messages about reserved slots are only shown when the server population is high so the message actually means something to people when it's shown. You can bypass this system for specific messages by including [whitelistbypass] including the brackets at the front of that message, then it will be shown to all players, use this for messages about events/giveaways/etc that you want everyone to see.
• Forgives could be issued against people who didn't have infraction points, this has been fixed.
• Added the /ping command, which will display a player's current and average ping in chat. You can just /ping to see your own ping info, or /ping playername to see another player's ping.
• Added the admin /fping command, which will force the layer to ping a player manually instead of trusting the server to ping them, this is more experimental and for giggles than anything else, but sometimes the layer is able to ping a player when their ping is missing.
• Players over 75 reputation now automatically contest reports against them.
• Extended round statistics (tbl_extendedroundstats) older than 60 days are automatically purged for performance reasons.
• Cleaned up some of the messages in the /reportlist command when players were offline.
• Fixed the issue where "command previous temp ban was not found in runaction" was spammed in the console due to an old BFAdminCP issue.
• Fixed issue where the fetch player perks command was marked as an admin command when it shouldn't have been.

This is available on the test branch at the moment, or if you issue a /pupdate.

 

Note to self, line 26890

Has it really been 7 months already? Man good times back then.

[ImportBot]

Originally Posted by AC-Topper*:

 

Hi,

 

nice to see that you're still working on this project. However, this update might explain why we have problems with our Procon layer since yesterday. The layer is responsible for two gameservers (BF3) but only one of them has AdKats enabled. After updating AdKats and starting up the layer, the non-AdKats server starts spamming this error message:

 

Code:

[AdKats] ERROR-69040: [Attempted to connect to database without all variables in place.]

At first, it only slows down the whole layer but sooner or later (seems like it depends on the server population), the layer crashes. Had to go back to 6.9.0.0 to get everything working properly again...

[ColColonCleaner]

Originally Posted by ColColonCleaner*:

 

Hi,

 

nice to see that you're still working on this project. However, this update might explain why we have problems with our Procon layer since yesterday. The layer is responsible for two gameservers (BF3) but only one of them has AdKats enabled. After updating AdKats and starting up the layer, the non-AdKats server starts spamming this error message:

 

Code:

[AdKats] ERROR-69040: [Attempted to connect to database without all variables in place.]

At first, it only slows down the whole layer but sooner or later (seems like it depends on the server population), the layer crashes. Had to go back to 6.9.0.0 to get everything working properly again...

That error means that the plugin (while already running) could not connect to the database because some of the connection information (username, password, etc) was deleted from the settings. Also, are you sure this only started yesterday? These changes have been over the course of about a week and a half, but if it only started yesterday I can isolate it to those changes.

 

The following version was released on the 15th (saturday) and there have been many updates since then. Could you please download and replace your current version with this one? It's 6.9.0.30.

 

Then, THIS IS IMPORTANT, mark the file as read-only on your layer so that AdKats cannot automatically update it to the latest test version. You will notice an occasional error that the plugin cannot update, just ignore it for the time being. Please get back to me if 6.9.0.30 still functions normally for you.

 

https://raw.githubusercontent.com/Ad...d8a4/AdKats.cs

[ImportBot]

Originally Posted by AC-Topper*:

 

That error means that the plugin (while already running) could not connect to the database because some of the connection information (username, password, etc) was deleted from the settings. Also, are you sure this only started yesterday? These changes have been over the course of about a week and a half, but if it only started yesterday I can isolate it to those changes.

Ingame admins have complained about bad layer performance since Sunday evening (european time) but I noticed this error yesterday. Maybe I haven't seen the connection to AdKats earlier due to the fact that it is only visible in the console of the non-AdKats server.

 

The following version was released on the 15th (saturday) and there have been many updates since then. Could you please download and replace your current version with this one? It's 6.9.0.30.

 

Then, THIS IS IMPORTANT, mark the file as read-only on your layer so that AdKats cannot automatically update it to the latest test version. You will notice an occasional error that the plugin cannot update, just ignore it for the time being. Please get back to me if 6.9.0.30 still functions normally for you.

 

https://raw.githubusercontent.com/Ad...d8a4/AdKats.cs

This version also causes the problem on our layer.

[ImportBot]

Originally Posted by optimusprimein*:

 

What changes you made bro?

 

 

Sent from my iPhone using Tapatalk

[ColColonCleaner]

Originally Posted by ColColonCleaner*:

 

Ingame admins have complained about bad layer performance since Sunday evening (european time) but I noticed this error yesterday. Maybe I haven't seen the connection to AdKats earlier due to the fact that it is only visible in the console of the non-AdKats server.

 

6.9.0.30 also causes the problem on our layer.

Please try the same with 6.9.0.24. Trying to isolate this. Also, what version were you on before you updated to .40? Were you still on 6.9.0.0?

 

https://raw.githubusercontent.com/Ad...ad60/AdKats.cs

[ImportBot]

Originally Posted by SmackDown*:

 

Thank you for working on Adkats again. It was nice to see you back here! Regarding the experimental tools, I hope you can find the time to make those item settings because those tools would be great to have. Also be sure when you release them that you provide documentation on how to use them for us people who don't know what the hell we are doing!

 

Thank you for your efforts....

[ColColonCleaner]

Originally Posted by ColColonCleaner*:

 

Thank you for working on Adkats again. It was nice to see you back here! Regarding the experimental tools, I hope you can find the time to make those item settings because those tools would be great to have. Also be sure when you release them that you provide documentation on how to use them for us people who don't know what the hell we are doing!

 

Thank you for your efforts....

As I mentioned above, keep the experimental section off until I have the time to make settings for the stuff it controls. There are a lot of automatic things enabled (or disabled) when you switch that on, even viewing the settings inside the experimental section turns things on/off.

 

People have been modifying the plugin to enable some of these things (which is allowed under GNU GPL) because even though the features are clearly displayed in the source, there were no settings built for them. I'm looking to make settings for them now.

 

Also, has anyone noticed performance issues with versions above 6.9.0.0 as AC-Topper has?

[ImportBot]

Originally Posted by AC-Topper*:

 

Hm, looks like the forum has blocked my recent post. Summed up, 6.9.0.30 does also cause this problem on our layer.

[ColColonCleaner]

Originally Posted by ColColonCleaner*:

 

Hm, looks like the forum has blocked my recent post. Summed up, 6.9.0.30 does also cause this problem on our layer.

Ah, looks like for some reason it moderated your posts. I could still see them though and i've approved them now. Did 6.9.0.24 work? the last one i posted.

[ColColonCleaner]

Originally Posted by ColColonCleaner*:

 

What changes you made bro?

 

 

Sent from my iPhone using Tapatalk

Changes from 6.9.0.0 til now have been noted in my previous post itemizing them all. Do you have a question about a specific item on that list?

[ImportBot]

Originally Posted by Sp0rAdiC*:

 

Also, has anyone noticed performance issues with versions above 6.9.0.0 as AC-Topper has?

Currently running 6.9.0.43 and everything seems to be running smooth for me. Thanks for your work on this.

[ImportBot]

Originally Posted by AC-Topper*:

 

Ah, looks like for some reason it moderated your posts. I could still see them though and i've approved them now. Did 6.9.0.24 work? the last one i posted.

Ok, let's see if this one gets blocked as well.

 

6.9.0.24 seems to work. No error message or performance issues after ~60 minutes.

 

Sorry, but I'm not sure how often or regularly the plugin has been updated (simply auto-updating from one test version to the next). Only went back to 6.9.0.0 because it is the easiest-to-find version that is stable.