Jump to content

Stov3top

Community Contributor
  • Content Count

    36
  • Joined

  • Last visited

About Stov3top

  • Rank
    Advanced Member

Contact Methods

  • Discord: -Stov3top-#7856

Profile Information

  • Gender
    Male

Recent Profile Visitors

44 profile views
  1. I havent messed with the plugin much, but I am pretty sure it is all covered in the plugin's main page. Check Here
  2. What kind of problems are you having? Make sure you have the latest ".def" file. If you go to the main maplist tab in procon, does all of the dlc show up in there to add to rotation?
  3. Looks like your SQL is still denying access. In order for me to get it to work I had to create an empty database in my cpanel with the database name I was going to use, add my username to have access to that database, then add that info (database name, user, and password) into the plugin and when activated it would populate the whole database with the tables. It wouldnt work without granting the user with permissions access to that database. I dont know if thats the case for you, but I hope that helps.
  4. Hardline Stats Page View File These are the stats pages to be used with the "Chat, GUID, Stats and Mapstats Logger". You will need version 1.5.3.x or later of procon that has the correct BFHL.def file. I have included 3 different styles to choose from: Red, Blue, or Hardline Yellow. You can find the sample pages as follows: Red Page Blue Page Yellow Page Submitter Stov3top Submitted 01/09/20 Category Plugin Enhancements  
  5. Version 2.0.0.0

    2 downloads

    These are the stats pages to be used with the "Chat, GUID, Stats and Mapstats Logger". You will need version 1.5.3.x or later of procon that has the correct BFHL.def file. I have included 3 different styles to choose from: Red, Blue, or Hardline Yellow. You can find the sample pages as follows: Red Page Blue Page Yellow Page
  6. Here is the latest website version with all but a couple of the weapons working. Download: Hardline Stats Webpage Demo Page: Stats Page Demo (Hardline Yellow)
  7. I ran into this issue the other day, the plugin would work fine in hardline, but threw this error in bf4. I switched to an older version of the plugin and it seemed to fix it. Try this one and see if it works for yours too. Older CChatGUIDStatsLogger
  8. Danny, not sure what the problem is as I dont have alot of experience with all of it, but I seen Tyger07 made some changes to one of the plugins to fix issues he was having with MySQL version 5.7.3 m13 and up. You might try this one and see if it helps. https://github.com/tyger07/CChatGUIDStatsLogger-1.0.0.2-ty_gerMOD
  9. If you want the older version, download that one and transfer all your config files back to that one. Just don't click to update that one.
  10. I have seen it pop up now and then on mine too, but it only does it every once in a while. It seems to work most of the time. Are you not getting any stats logged at all?
  11. Hmm, yeah that is odd. Maybe someone else could try to see if they run into the same issue. Running the updater manually works fine, was only when I tried to inside of procon.
  12. seen it calling for this file: "C:\Users\andre\Source\Repos\AdKats\Procon-1\src\". Is this a reference to your system? That could be why it works on yours and not mine.
  13. It downloaded the update, asked to restart to install, then this popped up. Same error on 2 machines. See the end of this message for details on invoking just-in-time (JIT) debugging instead of this dialog box. ************** Exception Text ************** System.BadImageFormatException: Could not load file or assembly 'C:\Users\Stov3top\Desktop\Procon 1.5.2.1\Updates\PRoConUpdater.exe' or one of its dependencies. This assembly is built by a runtime newer than the currently loaded runtime and cannot be loaded. File name: 'C:\Users\Stov3top\Desktop\Procon 1.5.2.1\Updates\PRoConUpdater.exe' at System.Reflection.AssemblyName.nGetFileInformation(String s) at System.Reflection.AssemblyName.GetAssemblyName(String assemblyFile) at PRoCon.Core.AutoUpdates.AutoUpdater.BeginUpdateProcess(PRoConApplication praApplication) in C:\Users\andre\Source\Repos\AdKats\Procon-1\src\PRoCon.Core\AutoUpdates\AutoUpdater.cs:line 406 at PRoCon.Forms.frmMain.toolStripDownloading_Click(Object sender, EventArgs e) in C:\Users\andre\Source\Repos\AdKats\Procon-1\src\PRoCon\Forms\frmMain.cs:line 562 at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e) at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e) at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e) at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea) at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks) at System.Windows.Forms.Control.WndProc(Message& m) at System.Windows.Forms.ToolStrip.WndProc(Message& m) at System.Windows.Forms.StatusStrip.WndProc(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) WRN: Assembly binding logging is turned OFF. To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1. Note: There is some performance penalty associated with assembly bind failure logging. To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog]. ************** Loaded Assemblies ************** mscorlib Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.9043 (WinRelRS5.050727-9000) ---------------------------------------- PRoCon Assembly Version: 1.5.2.1 Win32 Version: 1.5.2.1 ---------------------------------------- System.Windows.Forms Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.9038 (WinRelRS5.050727-9000) ---------------------------------------- System Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.9042 (WinRelRS5.050727-9000) ---------------------------------------- System.Drawing Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.9031 (WinRelRS5.050727-9000) ---------------------------------------- PRoCon.Core Assembly Version: 1.5.2.1 Win32 Version: 1.5.2.1 ---------------------------------------- System.Core Assembly Version: 3.5.0.0 Win32 Version: 3.5.30729.9034 built by: WinRelRS5 ---------------------------------------- System.Xml Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.9031 (WinRelRS5.050727-9000) ---------------------------------------- System.Configuration Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.9031 (WinRelRS5.050727-9000) ---------------------------------------- PRoConPluginEnumAssembly Assembly Version: 0.0.0.0 Win32 Version: 1.5.2.1 ---------------------------------------- PRoConPluginEnumAssembly Assembly Version: 0.0.0.0 Win32 Version: 1.5.2.1 ---------------------------------------- PRoConPluginEnumAssembly Assembly Version: 0.0.0.0 Win32 Version: 1.5.2.1 ---------------------------------------- PRoConPluginEnumAssembly Assembly Version: 0.0.0.0 Win32 Version: 1.5.2.1 ---------------------------------------- PRoConPluginEnumAssembly Assembly Version: 0.0.0.0 Win32 Version: 1.5.2.1 ---------------------------------------- PRoConPluginEnumAssembly Assembly Version: 0.0.0.0 Win32 Version: 1.5.2.1 ---------------------------------------- PRoConPluginEnumAssembly Assembly Version: 0.0.0.0 Win32 Version: 1.5.2.1 ---------------------------------------- PRoConPluginEnumAssembly Assembly Version: 0.0.0.0 Win32 Version: 1.5.2.1 ---------------------------------------- Accessibility Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.9031 (WinRelRS5.050727-9000) ---------------------------------------- System.Web Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.9031 (WinRelRS5.050727-9000) ---------------------------------------- System.Design Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.9038 (WinRelRS5.050727-9000) ---------------------------------------- Ionic.Zip.Reduced Assembly Version: 1.9.1.5 Win32 Version: 1.9.1.5 ---------------------------------------- ************** JIT Debugging ************** To enable just-in-time (JIT) debugging, the .config file for this application or computer (machine.config) must have the jitDebugging value set in the system.windows.forms section. The application must also be compiled with debugging enabled. For example: <configuration> <system.windows.forms jitDebugging="true" /> </configuration> When JIT debugging is enabled, any unhandled exception will be sent to the JIT debugger registered on the computer rather than be handled by this dialog box.
  14. Using the updater manually worked fine, I think it was when i tried to update in procon when the error happened.
×
×
  • Create New...

Important Information

Please review our Terms of Use and Privacy Policy. We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.