Advanced In-Game Admin and Ban Enforcer - AdKats

[ImportBot]

Originally Posted by sixpax12*:

 

https://github.com/AdKats

 

... if you click on the admin panel it is located in the install instructions towards the end.

[ColColonCleaner]

Originally Posted by ColColonCleaner*:

 

https://github.com/AdKats

 

... if you click on the admin panel it is located in the install instructions towards the end.

Ah yes the admincp project was moved under the AdKats group. I'm not sure where prophet wants the support page to link to so i'll let him handle that.

[Prophet731]

Originally Posted by Prophet731*:

 

... just a heads up the link to go for "help" on the admin panel in the installation instructions at github ( I know this is wrong forum, but could not find a separate thread for the admin panel ) is throwing a 404. I'm trying to figure out if you hit the startup.php link for initial setup or something else ?

 

https://www.adkgamers.com/forum/265-...b-dev-support/

Until I make a thread here on the myrcon forums i'll be using the AdKats thread here for temporary support questions.

 

But to answer your question, there isn't a "startup.php" file. You just need to follow the instructions on the README and it should automatically setup everything for you. I would recommend you run the latest version (2.1-dev) that I have up. If you have shell access to your web server I would recommend you follow the directions at the bottom of the page.

[ColColonCleaner]

Originally Posted by ColColonCleaner*:

 

AdKats 7.0.0.0 (15-OCT-2017)

 

This is the largest changelog AdKats has ever received. It contains the ~350 patches added since the release of 6.9.0.0 last year. Some of this is carry-over from the previous release since documentation was not updated at that time. Been tested for some time now but keep me posted with anything strange. Cheers.

 

If you are running 5.2.0.0+, your layer will automatically update and only require a reboot to run this version.

If not, update one layer, run it to complete startup, then repeat on your other layers.

 

https://sourceforge.net/projects/adk...atest/download

 

Enhancements

 

• When a player is kicked for VIP, the plugin is sometimes able to tell admins who was kicked. DICE's event for this is unreliable, but when it works properly, the plugin will tell admins about the VIP kick.
• Added automatic server restart options. When the server is empty (aside from seeder accounts), and the server uptime is greater than a configured number of hours, the server is automatically rebooted. You also have the option to do an automatic procon shutdown when this happens. If you have procon configured to automatically reboot when a crash/shutdown occurs this will effectively reboot your procon layer and the server at the same time.
• Increased performance of the anti-cheat scripts. AdKats now stores player's battlelog persona IDs in the database, so fetching their info from battlelog is faster and requires fewer requests.
• Decreased startup time of the loadout enforcer when paired with AdKats. Battlelog information needs to be fetched for every player before anti-cheat requests begin now.
• Commands that are classified as admin commands (commands that when enabled will make a role be considered admin), show up in the list with [ADMIN] next to them. Commands that are causing a role to be considered admin will have a '
• In addition to the "IRO Overrides Low Population" setting i've added a setting for minimum infractions before it overrides. With this setting a player will need at least that many infractions against them before IRO will override low population.
• Added a setting to disable the display of all ping enforcer messages in the procon chat tab. Messages for players kicked for ping are still displayed.
• The "Top Player Monitor" has been completely gutted and rebuilt. This section is now called the "Team Power Monitor" and shows the estimated power of each team in your server. You have options to use join reassignment based on team power and seeder balancing. The other sections of this system are either nonfunctional or experimental, and I would advise caution when using them. The scrambler might be good for your server, but it locks players to their assigned teams which means it's not good for volatile maps like metro.
• Added discord integration with the same options as the existing teamspeak integration. The only unfortunate side being that I can only update discord information (online players) every 5 minutes. This is because Procon is still on .NET 3.5 and doesn't have access to websockets.
• Admins can now bypass the spambot whitelist for certain messages by adding [whitelistbypass] to the start of the message. Useful for important/time-sensitive announcements.
• Added an all-caps chat limiter, with a bunch of settings for how a message is considered all-caps. Also added a new group so you can have only specific players targeted by this script.
• Completely redesigned the assist command for use with the team power monitor.
• Players that use the /assist command are now automatically queued for 5 minutes if their assist request fails. This is so players wanting to assist don't need to keep executing the command to see if they are allowed. After 5 minutes their assist request is automatically cancelled.
• A setting for the minimum number of minutes into a round before the /assist command becomes available has been added.
• Updated the assist messages to include a player's current calculated power.
• Added an option to disable the enforcement of single instances of AdKats on a server. This is for people who have issues with the /AdKatsInstanceCheck messages being stored in external systems. These messages are used by AdKats to make sure that one and only one instance is running on a server at a time, since it can cause undesirable results to have multiple instances running at the same time.
• Added a ban filter option for posting to metabans, so you can choose which bans are sent to the service.
• Add integration for PushBullet in the same manner that AdKats uses email integration.
• The nuke command can now accept team IDs in addition to team keys. This is mainly for people who run servers with the same faction as both teams and were previously unable to nuke team "2".
• The server shutdown command now provides a 5 second countdown before rebooting the server.
• Moved the auto-nuke settings into its own setting section so it's easier to configure.
• Added minimum and maximum ticket counts for the auto-surrender/auto-nuke so you can limit when it can activate during a round.
• The auto-nuke script is now able to issue timed nukes on players. This means a nuke is able to hold the target team's player dead for a specified amount of time, making the nuke more effective. I've also added options to increase the nuke duration as the number of times a team is nuked increases.
• Added options to reset the auto-nuke trigger counts when a nuke is fired, this way the script has time to reset after a nuked team loses a lot of flags.
• Added option for minimum duration between nukes to the auto-nuke script so you can configure how often it can fire.
• Added option to make nukes fire based on ticket difference instead of flags, so you can configure teams which have had the map for a long time to be pushed back regardless.
• Added option to configure how many nukes can fire during a round.
• Added option to switch back to auto-surrender after a certain number of nukes are fired and the team is still having trouble.
• Added an optional countdown before an auto-nuke is actually fired, giving players a chance to realize what's about to happen.
• Added option to notify players of perks that are expiring soon. Included the new /perks command so they can see what perks they have. Included a setting for how long before their perks expire to notify them.
• Added the "Battlecry" system. This section lets you allow players have a message sent to the server when they first spawn in, an announcement of their arrival. Options are available to change how "loud" the messages are and who is able to access their usage. You can also configure a list of banned words in the battlecry, and a max length on the battlecry.
• Added a BF4 faction randomizer so you can have random faction assignments in your server. There are many options for how the randomness should be handled.
• Split the 'Inform reputable players and admins of admin joins' into two separate settings, one for reputable players, and one for admins.
• Updated all the procon chat messages AdKats posts to be color coded for different operations. Added tags for some things like the spambot so its messages can be picked out of the tab easily.
• Messages in your rules and spambot can now be map/mode specific. Simply by adding a prefix to the messages and rules you can make them appear only on those maps or modes. Great for mixed mode servers.
• AdKats now monitors player clan tag changes, keeps a history of them, and notifies admins of changes. Tag history is also included in the player info command.
• Added domination to the list of modes where flag estimations are shown in the ticket rate messages.
• Added estimated winner and win time to the ticket rate messages.
• In BF4 since the in-game menu does not tell players why they were kicked or banned anymore, so AdKats now spams the kicked or banned player for a few seconds before they are booted to make sure they know why it happened.
• Improved some of the integrations with the loadout enforcer plugin. Specifically for report actions and manual loadout fetching.
• Added %map_name% and %mode_name% options to the email handler for reports.
• Improved the player info command to show actual hour count the player has in the server, in addition to the calculated weeks/days/hours string.
• Cleaned up quite a few messages which were unnecessarily long.
• Added more robust monitoring of player listing and server info triggers, making sure AdKats doesn't oversaturate procon or the server with requests.
• Fortified exception handling in a lot of areas.
• Average AdKats startup durations are stored for the last 15 reboots, and displayed in the startup message when it fully completes.
• Estimated time until the plugin is finished starting up are now displayed to players attempting to issue commands during the startup phase. Once startup has completed they are notified and thanked for their patience.

New Commands

 

• server_nuke_winning - Added a winning-nuke command, which is only able to nuke the currently winning and map dominant team. Helps to avoid human error when manually issuing nukes.
• player_ping - You can now fetch any player's current ping and average ping with the fetch ping command.
• player_forceping - Admins can now force AdKats to issue manual pings on specific players using the force ping command. These players will be manually pinged by the layer instead of relying on the server provided info on their ping.
• player_debugassist - The debug assist command was added mainly for my own purposes, so i can see if a player would be allowed to assist without actually having them do it. But it could be useful to some people.
• player_perks - Players are now able to fetch their current list of perks with the player perks command. This command can also be targeted at a player to fetch that player's perks.
• player_loadout - You can now fetch a player's current loadout if you're running the loadout enforcer, using the loadout command.
• player_loadout_force - Players loadouts can now be manually forced up to trigger level enforcement if you're running the loadout enforcer, with the force loadout command.
• self_battlecry - Players can set their own battlecry using the battlecry command.
• player_battlecry - Admins can use the player battlecry command to set other player's current battle cries.
• player_discordlink - Admins can link an active player in the server with a member in the discord server by ID using the discord link command.
• player_blacklistallcaps - Admins can make specific players fall under enforcement of the all caps chat limiter using the all caps blacklist command.
• player_blacklistallcaps_remove - Admins can remove players from the all caps blacklist specific enforcement using the remove all caps blacklist command.

Changes

 

• Reserved slot feed for *online* admins has been renamed to match what it actually does, add a VIP kick whitelist.
• Weapon code posting to the centralized weapon code display has been removed since all weapon codes for the supported games are known now.
• Everything that was previously named "Hacker-Checker" is now named "Anti-Cheat". The command /hcwhitelist is also renamed to /acwhitelist to go along with this change.
• Players in teamspeak/discord are now automatically whitelisted from spambot messages.
• Automatic forgives for clean play no longer require positive reputation.
• Changed a lot of messages around the plugin which used a team's name/key to also include the team ID in the message in the format ID/Key.
• The 'time on server' section of the player info command no longer says '+ current session'. The current session time is simply added to the base and displayed now.
• The mark command is no longer used to force player loadouts, there is a separate command for that now. The mark command is now only used to mark a player for leave notifications.
• Removed the concept of 'adjusted' ticket rates from the UI. The rates shown to you for flag based modes are now by default the adjusted rates, normal rates are shown for non-map modes.
• Added a block against negative values in the minimum surrender/auto-nuke ticket gap setting.
• Added block against people adding a minimum ticket rate window value greater than the maximum ticket rate window value, and vice-versa. The values will now automatically swap when the user attempts this.
• Records in the extended round stats table older than 60 days are now automatically purged.
• First join/first spawn messages are now blocked when the plugin is recently started. This is to make sure that players are not spammed when you reboot the plugin during an active round.
• Player leave notifications are no longer given based on private say/yell/tell messages through AdKats, all other action commands still result in a notification.
• Kicks against yourself are no longer announced to the server.
• Ticket rates in procon chat are now only displayed during an active round where ticket counts have changed, before they would still display during the pre-round phase.
• Forgiving players into negative infraction point values is now blocked.
• Replaced all mentions of @command in the plugin with !command.
• Issuing the kill command on a player will now announce that action to the server like other actions do.
• Removed messages about global timing fetch errors.
• Removed the restrictions on player names which were in place for BF3. Now most characters can be used in player names. The unfortunate side of this is those characters still cause issue fetching from battlelog.
• Changed population success notification to be a tell instead of a say.
• The players ColColonCleaner and PhirePhrey are automatically added to reserved slots for any server running AdKats.
• IP-API communication errors are now changed to debug messages instead of error messages, since they are not crucial to the function of AdKats.

Bugs Fixed

 

• Fixed an issue where players could end up being infinitely queued for anti-cheat checks if their battlelog info was unavailable.
• Fixed an issue where players would not get updated battlelog information after the first fetch was complete, specifically on new rounds.
• Fixed an issue where players could end up being infinitely queued for IP info fetches if the server failed to respond, or if they left the server before it did.
• Fixed an issue where errors were thrown because some player's battlelog information exceeded the size of 32 bit integers, increased the size of those variables.
• Fixed the DPS ban messages to contain the proper code 4 prefix.
• Fixed the KPM ban messages to contain the proper code 5 prefix.
• Fixed an issue where modifying a role's authorized commands would shoot you back to the top of the setting list. Basically now it waits a while before modifying the tags on those settings in the procon view.
• Fixed an issue where allowing commands from muted players would allow them to simply place a command prefix in front of the message and it wouldn't act on them. Now it confirms that the command is valid and exists.
• Assist command timeout had incorrect calculations due to the duration of the command. This has been fixed.
• Fixed an issue where sometimes players could spawn while a nuke is happening and remain alive.
• Fixed some of the message formatting sent by the active round reports command.
• Fixed an issue where surrender voting included spectators/commanders in the required player count calculation to surrender.
• Fixed an issue where the populator monitor would not fetch updated populator players immediately when that section was enabled, it would have to wait for the next user list update (5 minute interval).
• Fixed chat spam during off hours caused by the spambot, making sure that those messages are only visible in the chat tab when there are at least 5 players in the server.
• Fixed issue where AFK player monitor would count all players (commanders/spectators) instead of just the active round players.
• Fixed an issue where AdKats and some auto-balancer plugins could fight over where a player should be if an admin moved them. AdKats would never give up the fight for control of the player and that resulted in an infinite loop of swapping the player between teams. AdKats now gives up the fight if a players has 8 or more moves in 5 seconds.
• Fixed an issue where a player who was previously assigned a team leaving the server would delete their assigned team, allowing them to join back and switch to their original team. AdKats now remembers their assigned team when the leave and rejoin during a single round.
• Fixed an issue where using section 4-2 to add command target whitelist to a role would have no effect.
• Fixed an issue where players were able to use the join command on themselves to get a free admin kill. They were also able to use this on a current squadmate for the same reason. These are now blocked.
• Blocked usage of the join/pull commands from spectator and commander player types.
• Fixed an issue where 'previous' bans could end up being imported into the plugin. The bans wouldn't be issued again but it caused unnecessary processor work.
• Fixed an issue where a player could be added to multiple users at the same time.
• Fixed player fetch performance in several scenarios. Sometimes a player which was already loaded was still fetched from the database again.
• Fixed a bug where admin assistants who were considered 'grandfathered' would cause fetching issues.
• Fixed an issue where the spectator slot feed would attempt to add more than 15 players to the list. For some reason DICE added a 15 player limit to the spectator slot list. When you have more than 15 approved spectators now it just manually monitors the list and keeps the official spectator list empty.
• Fixed a few error possibilities coming from the ping enforcer.
• Fixed an error where comparing command input with player names could crash.
• Removed extra message spam caused by the private messaging system.
• Removed extra message spam caused by player say/yell/tell commands issued by external plugins.
• Fixed shutdown durations in some cases, making sure threads automatically exit when you shut down the plugin.
• Fixed an issue where battlelog going offline would cause a lot of errors to be thrown by the plugin. Now the plugin will wait at 30 second intervals and show warnings if battlelog is offline.
• Fixed an issue where the admin assistant whitelist could be given to admin roles in section 4-2. That whitelist is not supposed to be used for admin roles.
• Fixed an issue where the !help command would return commands which were supposed to be background commands.

Upgrade SQL from 4.0.0.0 - Current

 

No manual upgrade SQL required.

[ImportBot]

Originally Posted by Hodor*:

 

Looks good i will test it as soon as possible.

[ImportBot]

Originally Posted by sixpax12*:

 

No issues thus far ... updated across several servers yesterday.

[ImportBot]

Originally Posted by bartbart*:

 

[18:07:26 14] [AdKats] EXCEPTION-7000-D-BuildRoleSettings-Main9: [Error building role setting section.][system.Collections.Generic.KeyNotFoundException: Der angegebene Schlüssel war nicht im Wörterbuch angegeben.

bei System.ThrowHelper.ThrowKeyNotFoundException()

bei System.Collections.Generic.Dictionary`2.get_Item(T Key key)

bei PRoConEvents.AdKats.BuildRoleSettings(List`1 lstReturn)]

[ColColonCleaner]

Originally Posted by ColColonCleaner*:

 

[18:07:26 14] [AdKats] EXCEPTION-7000-D-BuildRoleSettings-Main9: [Error building role setting section.][system.Collections.Generic.KeyNotFoundException: Der angegebene Schlüssel war nicht im Wörterbuch angegeben.

bei System.ThrowHelper.ThrowKeyNotFoundException()

bei System.Collections.Generic.Dictionary`2.get_Item(T Key key)

bei PRoConEvents.AdKats.BuildRoleSettings(List`1 lstReturn)]

I think I've found the issue. This error might show up if you're adding new roles to the plugin. Never ran into it during testing because the roles on my testing server have been static for a long time.

 

To fix the error temporarily after adding a new role, try rebooting the procon player.

 

Until it's fixed this error will only stop the roles setting section from displaying, the rest of the plugin will function normally.

[ImportBot]

Originally Posted by sixpax12*:

 

BFAdminCP-master question ...

 

What do I make this (Line 17 of autoload.php ) :

 

require __DIR__.'/../vendor/autoload.php';

 

... to prevent this:

 

[14-Oct-2017 14:18:24 UTC] PHP Fatal error: require(): Failed opening required 'C:\Inetpub\vhosts\xxx.org\info.xxx.org\BFAdminCP-master\bootstrap/../vendor/autoload.php' (include_path='.;.\includes;.\pear') in C:\Inetpub\vhosts\xxx.org\info.xxx.org\BFAdminCP-master\bootstrap\autoload.php on line 17

 

... I am guessing this ?

 

require __DIR__.'/autoload.php';

[ImportBot]

Originally Posted by klait68*:

 

Is there a possibility to add another discord-option: If a player was banned and kicked from server to post it via discord in an discord channel ?

[ColColonCleaner]

Originally Posted by ColColonCleaner*:

 

Is there a possibility to add another discord-option: If a player was banned and kicked from server to post it via discord in an discord channel ?

Not until Procon is updated to a newer version of .NET, which might be possible for newer versions of AdKats. Releasing a 'beta' version of procon on the newer .NET releases but keeping the old version available for backwards compatibility purposes.

[ColColonCleaner]

Originally Posted by ColColonCleaner*:

 

This is the version i'm looking to test:

https://github.com/I-MrFixIt-I/Procon-1/tree/dotnet-4.7

I-MrFixIt-I modified the procon project for .NET 4.7 and added UTF-8 support

 

If testing goes well for AdKats, stat logger, insane limits, and multibalancer it should be fine for all other BF4/BF3 plugins since these are the most intrusive plugins for utilizing procon functions. And I'll push that to the admins for accepting as a beta release (if not a full release).

 

Then I will be able to do a lot more things I couldn't do before. The first being FINALLY fixing the URL encoding of non-standard player names with battlelog since they can have special characters in them now. Secondly implementing proper Discord integration with WebSockets.

[ImportBot]

Originally Posted by Sp0rAdiC*:

 

Is there a possibility to add another discord-option: If a player was banned and kicked from server to post it via discord in an discord channel ?

I do have mine setup to do this although it does take a few steps.

 

First I use showthread....hlight=banfeed* to create an XML feed.

 

Create a new webhook in Discord.

 

Then use zapier.com to POST the RSS feed to the webhook you just created.

[ImportBot]

Originally Posted by Chilace*:

 

Not until Procon is updated to a newer version of .NET, which might be possible for newer versions of AdKats. Releasing a 'beta' version of procon on the newer .NET releases but keeping the old version available for backwards compatibility purposes.

You don't need websockets to post such of data, but http/rest api. Isn't it?

 

I do have mine setup to do this although it does take a few steps.

 

First I use showthread....hlight=banfeed* to create an XML feed.

 

Create a new webhook in Discord.

 

Then use zapier.com to POST the RSS feed to the webhook you just created.

Just want to mention an alternative service - ifttt.com

Despite the fact that the zapier.com is more functional their free plan is limited.

 

There is another option using the ability of the InsaneLimits to post to Twitter (for examle: https://twitter.com/InsaneLimits) and then post that tweets to Discord webhook through Zapier or IFTTT.

[ColColonCleaner]

Originally Posted by ColColonCleaner*:

 

You don't need websockets to post such of data, but http/rest api. Isn't it?

The only thing available over http/rest is their widgets.json URL for each server which is cached, and that cache is invalidated at a 5 minute interval. All other communication requires websockets. I've confirmed this with the discord API devs.

[ImportBot]

Originally Posted by Chilace*:

 

The only thing available over http/rest is their widgets.json URL for each server which is cached, and that cache is invalidated at a 5 minute interval. All other communication requires websockets. I've confirmed this with the discord API devs.

Websockets need to sync with players, channels, for using bots etc. but for posting baninfo into channel trough webhook you only have to post simple http post request with json string in body to webhook endpoint: https://discordapp.com/api/webhooks/{webhook.id}/{webhook.token}.

Similar to how you did it with pushbullet.

 

Intro to Webhooks: https://support.discordapp.com/hc/en...ro-to-Webhooks

 

Also see my previous posts:

myrcon.net/...advanced-in-game-admin-and-ban-enforcer-adkats#entry42247

myrcon.net/...advanced-in-game-admin-and-ban-enforcer-adkats#entry42250

myrcon.net/...advanced-in-game-admin-and-ban-enforcer-adkats#entry42272

 

P.S. May be better to implement this feature on the backend of the BFAdminCP

P.P.S. Just temporary create test webhook on your server and tell me his url in options & I'll send "hello world" to you channel without authorization and websokets.

[ColColonCleaner]

Originally Posted by ColColonCleaner*:

 

Websockets need to sync with players, channels, for using bots etc. but for posting baninfo into channel trough webhook you only have to post simple http post request with json string in body to webhook endpoint: https://discordapp.com/api/webhooks/{webhook.id}/{webhook.token}.

Similar to how you did it with pushbullet.

 

Intro to Webhooks: https://support.discordapp.com/hc/en...ro-to-Webhooks

 

Also see my previous posts:

myrcon.net/...advanced-in-game-admin-and-ban-enforcer-adkats#entry42247

myrcon.net/...advanced-in-game-admin-and-ban-enforcer-adkats#entry42250

myrcon.net/...advanced-in-game-admin-and-ban-enforcer-adkats#entry42272

 

P.S. May be better to implement this feature on the backend of the BFAdminCP

P.P.S. Just temporary create test webhook on your server and tell me his url in options & I'll send "hello world" to you channel without authorization and websokets.

Ah yes, i had forgotten what the discussion with the devs was actually about. Websockets were required to get information FROM the server, member names, their presence in voice channels etc, at a faster rate than every 5 minutes. You can still use this method for posting data TO discord. Didn't remember that detail.

[ImportBot]

Originally Posted by Hodor*:

 

This is the version i'm looking to test:

https://github.com/I-MrFixIt-I/Procon-1/tree/dotnet-4.7

I-MrFixIt-I modified the procon project for .NET 4.7 and added UTF-8 support

 

If testing goes well for AdKats, stat logger, insane limits, and multibalancer it should be fine for all other BF4/BF3 plugins since these are the most intrusive plugins for utilizing procon functions. And I'll push that to the admins for accepting as a beta release (if not a full release).

 

Then I will be able to do a lot more things I couldn't do before. The first being FINALLY fixing the URL encoding of non-standard player names with battlelog since they can have special characters in them now. Secondly implementing proper Discord integration with WebSockets.

Can he optimize this for working with Linux or through Mono?

[ColColonCleaner]

Originally Posted by ColColonCleaner*:

 

Can he optimize this for working with Linux or through Mono?

I don't think there is any current work being done to further procon on the Linux platform.

 

Sent from my SM-G920P using Tapatalk

[ImportBot]

Originally Posted by Hodor*:

 

@ColColonCleaner

How to download 1.5.2.0 ?

[ColColonCleaner]

Originally Posted by ColColonCleaner*:

 

@ColColonCleaner

How to download 1.5.2.0 ?

Don't, it's not tested.

[ImportBot]

Originally Posted by Hodor*:

 

@ColColonCleaner

I understand that this can be unstable, but please let me test this as it will work on my system with Mono. Can you give me a link in PM?

[Prophet731]

Originally Posted by Prophet731*:

 

BFAdminCP-master question ...

 

What do I make this (Line 17 of autoload.php ) :

 

require __DIR__.'/../vendor/autoload.php';

 

... to prevent this:

 

[14-Oct-2017 14:18:24 UTC] PHP Fatal error: require(): Failed opening required 'C:\Inetpub\vhosts\xxx.org\info.xxx.org\BFAdminCP-master\bootstrap/../vendor/autoload.php' (include_path='.;.\includes;.\pear') in C:\Inetpub\vhosts\xxx.org\info.xxx.org\BFAdminCP-master\bootstrap\autoload.php on line 17

 

... I am guessing this ?

 

require __DIR__.'/autoload.php';

Looks like you're running it on IIS web server correct? That error is actually suppose to happen because you're missing the vendor folder. Download it from sourceforge as that's where the actual builds are put. Here is the latest link to get it. Also I never really fully tested it on IIS since I never run that software. It should come with the web.config for it that I made a while back.

[ColColonCleaner]

Originally Posted by ColColonCleaner*:

 

@ColColonCleaner

I understand that this can be unstable, but please let me test this as it will work on my system with Mono. Can you give me a link in PM?

Here is the built test version running .NET 4.7.

 

Attached Files:

• ProconNET47Test.zip

[ImportBot]

Originally Posted by sixpax12*:

 

Looks like you're running it on IIS web server correct? That error is actually suppose to happen because you're missing the vendor folder. Download it from sourceforge as that's where the actual builds are put. Here is the latest link to get it. Also I never really fully tested it on IIS since I never run that software. It should come with the web.config for it that I made a while back.

thank you for response. i had downloaded the github version under adkats ... there was no vendor folder in that ... i will upload the version from your link provided above and try to get it running ... yes indeed IIS ...

[Prophet731]

Originally Posted by Prophet731*:

 

thank you for response. i had downloaded the github version under adkats ... there was no vendor folder in that ... i will upload the version from your link provided above and try to get it running ... yes indeed IIS ...

Yeah I don't include it on github cause it's just a pain to keep updated on that. So I have it do it when I publish a release.

 

Sent from my ONEPLUS A3000 using Tapatalk

[ColColonCleaner]

Originally Posted by ColColonCleaner*:

 

Hello,

 

Today I rebooted my layer servers and upgraded Adkats to version 7.0.0.3. During reboot, I noticed the following in the counsel as Adkats was reloading up:

 

[05:40:05 48] [AdKats] INFO: OS: Win32NT | 6.1.7601.65536 | Microsoft Windows NT 6.1.7601 Service Pack 1

[05:40:05 48] [AdKats] INFO: DLLPath: c:\games\\962102\procon\Plugins\BF4

[05:40:05 48] [AdKats] INFO: PluginPath: c:\games\\962102\procon\Plugins\BF4\AdKats.cs

[05:40:05 48] [AdKats] INFO: PluginPath2: c:\games\\962102\procon\Plugins\BF4\AdKats.cs

 

Can someone tell me what this means? Is this something that I need to worry about or is it just a change made to the database with Adkats?

 

Thank you in advance for your efforts.

Removed the server IP addresses from your post.

 

Those are debug messages when you manually issue a plugin update that will help determine what's going wrong with plugin updates on Linux. They show the os version and the generated plugin paths.

 

Hodor is currently using these messages.

 

EDIT: You didn't need to delete your post SmackDown, i had already edited it to remove the information.

[ImportBot]

Originally Posted by sixpax12*:

 

Yeah I don't include it on github cause it's just a pain to keep updated on that. So I have it do it when I publish a release.

 

Sent from my ONEPLUS A3000 using Tapatalk

We were sailing along with install and looks like it was just about to display the dashboard and we got:

 

Whoops, looks like something went wrong.

 

There is nothing in my php error log so not sure what is wrong.

[ColColonCleaner]

Originally Posted by ColColonCleaner*:

 

Hodor, i need those messages from your server.

[ImportBot]

Originally Posted by Hodor*:

 

@ColColonCleaner

 

What kind of messages? No errors, testing right now AdKats 7.0+ | PRoCon chat, guid logger | ProconRulz | MULTIbalancer.

I launched it with mono 4.8.1.0. It is easy to get this version:

Code:

yum install yum-utils
rpm --import "http://keyserver.ubuntu.com/pks/lookup_op=get&search=0x3FA7E0328081BFF6A14DA29AA6A19B38D3D831EF"
yum-config-manager --add-repo http://download.mono-project.com/repo/centos7/

yum install mono-complete-4.8.1.0