Administrators Prophet731 Posted November 16, 2019 Administrators Share Posted November 16, 2019 This release has been upgraded to the .NET Framework 4.7. You will need to have that version installed in order to run all versions past 1.5.3.0. This will be released next week on Friday (11/22/19). If you are already running version 1.5.2.1 then it should prompt you for this update. Follow this topic to be notified when it's released if you haven't upgraded yet to 1.5.2.1 Changes Compiled for .NET Framework 4.7 Added missing BFHL definitions Docker Support Also in this version I will hopefully have a docker version available for procon. This is for the more advanced users but I think it would be worth it. This is also my first attempt at building a docker image so expect problems with my noobness. You can try out the docker stuff here https://github.com/AdKats/Procon1Docker Needs more documentation but it's there. Download https://myrcon.net/topic/2-procon-1x/ The developer of the Battlefield Admin Control Panel (BFACP) For BFACP support please post in the BFACP topic linked above. Do not contact me via PM on the forums for help with procon. Please make a topic for it. Only PM's I will accept will revolve around any website issues. Link to comment
Timm Posted November 17, 2019 Share Posted November 17, 2019 What benefits will this version get? Better optimization or? Or is it a release, just not to use the old version of .NET and just optimized to .NET 4.7? Link to comment
Administrators Prophet731 Posted November 17, 2019 Author Administrators Share Posted November 17, 2019 4.x version was supposed to be released years ago but it never did. We're just releasing a 4.7 version so it uses the latest version dotnet framework. It was mostly issues with windows 10 not having 3.5 installed. Besides doesn't hurt to be up-to-date. Hopefully all goes well because plugins are not tested with this framework. The developer of the Battlefield Admin Control Panel (BFACP) For BFACP support please post in the BFACP topic linked above. Do not contact me via PM on the forums for help with procon. Please make a topic for it. Only PM's I will accept will revolve around any website issues. Link to comment
Administrators Prophet731 Posted November 17, 2019 Author Administrators Share Posted November 17, 2019 Added docker support notes. The developer of the Battlefield Admin Control Panel (BFACP) For BFACP support please post in the BFACP topic linked above. Do not contact me via PM on the forums for help with procon. Please make a topic for it. Only PM's I will accept will revolve around any website issues. Link to comment
Hedius Posted November 17, 2019 Share Posted November 17, 2019 I have a few suggestions for the docker version Do not run procon as root (it is good practise to run applications with an user that does not exist on the host system). This ensures that software that manages to escape the container is not automatically root on the docker host. ARG UID=5000 ARG GID=5000 # account for execution RUN groupadd -r -g $GID procon && \ useradd -r -g procon -u $UID procon && \ chown procon:procon -R /procon # switch user USER procon:procon Your setup does not allow updates of the container. I would use volumes for the config and plugins, because those folders should be persistent over updates. Otherwise you will lose changes between container updates. VOLUME ["/procon/Configs", "/procon/Plugins"] ADD ConfigsADD Pluginsadd both folders to the container, but changes are only saved within the container. So changes to plugin settings will be lost. An option would be: rm Configs && Plugins within the Docker image/Dockerfile mount ./Configs to /procon/Configs mount ./Plugins to /procon/Plugins It would be possibly to mount the volumes so: docker run: -v localPath:RemotePath docker-compose: volumes: - ./Configs:/procon/Configs - ./Plugins:/procon/Plugins Here is an example how I use procon in docker: (P.S.: The procon.zip is stored locally, because well myrcon was down in the past). I use docker volumes. The data is then located at /var/lib/docker/volumes/name/_data/ DockerFile: # Docker PRoCon Image # Creator: H3dius/Hedius [email protected] FROM mono:latest # user and group ID of the account for full read/write access ARG UID=10000 ARG GID=10000 ARG FILE="procon_1.5.1.1.zip" LABEL maintainer="Hedius @ gitlab.com/hedius" \ description="PRoCon Docker image" \ version="1.0" # install unzip RUN apt-get update && apt-get install -y unzip # account for execution RUN groupadd -r -g $GID procon && \ useradd -r -g procon -u $UID procon #Set the workdirectory WORKDIR /opt/procon ADD --chown=procon:procon $FILE . RUN unzip $FILE && \ chown procon:procon -R /opt/procon && \ rm -r Configs Plugins $FILE USER procon:procon VOLUME ["/opt/procon/Configs", "/opt/procon/Plugins"] ENTRYPOINT ["mono", "PRoCon.Console.exe"] docker-compose.yml version: '2.4' services: procon1: container_name: procon1 build: context: . image: hedius/procon:1.0 restart: unless-stopped ports: - "13001:13000" volumes: - type: volume source: config1 target: /opt/procon/Configs - type: volume source: plugin1 target: /opt/procon/Plugins - type: volume source: log1 target: /opt/procon/Logs security_opt: - no-new-privileges tty: true mem_limit: 3G mem_reservation: 2500M volumes: config1: plugin1: log1: Need new plugin features? I can change: Adkats, AdKatsLRT, LanguageEnforcer, InsaneLimits, xVotemap for you. Also working on new plugins. Have an idea? Share it and I might include it in my repos. Github.com/hedius Check out E4GLAdKats for an advancded and maintained AdKats version. Link to comment
Administrators Prophet731 Posted November 18, 2019 Author Administrators Share Posted November 18, 2019 I have a few suggestions for the docker version Do not run procon as root (it is good practise to run applications with an user that does not exist on the host system). This ensures that software that manages to escape the container is not automatically root on the docker host. ARG UID=5000 ARG GID=5000 # account for execution RUN groupadd -r -g $GID procon && \ useradd -r -g procon -u $UID procon && \ chown procon:procon -R /procon # switch user USER procon:procon Your setup does not allow updates of the container. I would use volumes for the config and plugins, because those folders should be persistent over updates. Otherwise you will lose changes between container updates. VOLUME ["/procon/Configs", "/procon/Plugins"] ADD Configs ADD Plugins add both folders to the container, but changes are only saved within the container. So changes to plugin settings will be lost. An option would be: rm Configs && Plugins within the Docker image/Dockerfile mount ./Configs to /procon/Configs mount ./Plugins to /procon/Plugins It would be possibly to mount the volumes so: docker run: -v localPath:RemotePath docker-compose: volumes: - ./Configs:/procon/Configs - ./Plugins:/procon/Plugins Here is an example how I use procon in docker: (P.S.: The procon.zip is stored locally, because well myrcon was down in the past). I use docker volumes. The data is then located at /var/lib/docker/volumes/name/_data/ DockerFile: # Docker PRoCon Image # Creator: H3dius/Hedius [email protected] FROM mono:latest # user and group ID of the account for full read/write access ARG UID=10000 ARG GID=10000 ARG FILE="procon_1.5.1.1.zip" LABEL maintainer="Hedius @ gitlab.com/hedius" \ description="PRoCon Docker image" \ version="1.0" # install unzip RUN apt-get update && apt-get install -y unzip # account for execution RUN groupadd -r -g $GID procon && \ useradd -r -g procon -u $UID procon #Set the workdirectory WORKDIR /opt/procon ADD --chown=procon:procon $FILE . RUN unzip $FILE && \ chown procon:procon -R /opt/procon && \ rm -r Configs Plugins $FILE USER procon:procon VOLUME ["/opt/procon/Configs", "/opt/procon/Plugins"] ENTRYPOINT ["mono", "PRoCon.Console.exe"] docker-compose.yml version: '2.4' services: procon1: container_name: procon1 build: context: . image: hedius/procon:1.0 restart: unless-stopped ports: - "13001:13000" volumes: - type: volume source: config1 target: /opt/procon/Configs - type: volume source: plugin1 target: /opt/procon/Plugins - type: volume source: log1 target: /opt/procon/Logs security_opt: - no-new-privileges tty: true mem_limit: 3G mem_reservation: 2500M volumes: config1: plugin1: log1: Made some of this changes in the develop branch. The developer of the Battlefield Admin Control Panel (BFACP) For BFACP support please post in the BFACP topic linked above. Do not contact me via PM on the forums for help with procon. Please make a topic for it. Only PM's I will accept will revolve around any website issues. Link to comment
Stov3top Posted November 18, 2019 Share Posted November 18, 2019 Great, thanks for the continued support for all of this. Link to comment
Timm Posted November 21, 2019 Share Posted November 21, 2019 Will check tomorrow, thank you for you work and update. Link to comment
Stov3top Posted November 21, 2019 Share Posted November 21, 2019 Only issue I ran into was trying to update from the older one, threw up an error about using a newer version (assuming .net framework) Other than that everything seems to be running great, thanks again. Link to comment
Stov3top Posted November 21, 2019 Share Posted November 21, 2019 Using the updater manually worked fine, I think it was when i tried to update in procon when the error happened. Link to comment
Administrators Prophet731 Posted November 21, 2019 Author Administrators Share Posted November 21, 2019 It threw up an error about needing. Net 4.7? Sent from my ONEPLUS A5010 using Tapatalk The developer of the Battlefield Admin Control Panel (BFACP) For BFACP support please post in the BFACP topic linked above. Do not contact me via PM on the forums for help with procon. Please make a topic for it. Only PM's I will accept will revolve around any website issues. Link to comment
Stov3top Posted November 21, 2019 Share Posted November 21, 2019 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. Link to comment
Administrators Prophet731 Posted November 22, 2019 Author Administrators Share Posted November 22, 2019 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. I just tried this on one of my windows vms and it updated without an issue. Might have been something unique to your system setup. The developer of the Battlefield Admin Control Panel (BFACP) For BFACP support please post in the BFACP topic linked above. Do not contact me via PM on the forums for help with procon. Please make a topic for it. Only PM's I will accept will revolve around any website issues. Link to comment
Stov3top Posted November 22, 2019 Share Posted November 22, 2019 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. Link to comment
Administrators Prophet731 Posted November 22, 2019 Author Administrators Share Posted November 22, 2019 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. Yes it is my system but I doubt it. The windows vm doesn't have a user account under that name and it was ran under the Administrator account. The developer of the Battlefield Admin Control Panel (BFACP) For BFACP support please post in the BFACP topic linked above. Do not contact me via PM on the forums for help with procon. Please make a topic for it. Only PM's I will accept will revolve around any website issues. Link to comment
Stov3top Posted November 22, 2019 Share Posted November 22, 2019 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. Link to comment
B7ackhawk Posted November 24, 2019 Share Posted November 24, 2019 Hello guys i have problem with procon cant update https://prnt.sc/q18z5y Link to comment
Administrators Prophet731 Posted November 24, 2019 Author Administrators Share Posted November 24, 2019 Hello guys i have problem with procon cant update https://prnt.sc/q18z5y Run the updater file located in the procon folder. That should work as stated above by stove3top. If not just download the one from the download section and overwrite everything in your current install folder. The developer of the Battlefield Admin Control Panel (BFACP) For BFACP support please post in the BFACP topic linked above. Do not contact me via PM on the forums for help with procon. Please make a topic for it. Only PM's I will accept will revolve around any website issues. Link to comment
B7ackhawk Posted November 25, 2019 Share Posted November 25, 2019 is there any problem with this update ? i update all my insane-limits setting give error one of m setting Link to comment
Administrators Prophet731 Posted November 25, 2019 Author Administrators Share Posted November 25, 2019 is there any problem with this update ? i update all my insane-limits setting give error one of m setting The update checker in insane limits is checking the domain "forum.myrcon.com" which no longer exists. Anything "*.myrcon.com" will not resolve. The developer of the Battlefield Admin Control Panel (BFACP) For BFACP support please post in the BFACP topic linked above. Do not contact me via PM on the forums for help with procon. Please make a topic for it. Only PM's I will accept will revolve around any website issues. Link to comment
B7ackhawk Posted November 25, 2019 Share Posted November 25, 2019 is there any problem with this update ? i update all my insane-limits setting give error one of m setting well how i solve this problem ? sorry for bad english Link to comment
Administrators Prophet731 Posted November 25, 2019 Author Administrators Share Posted November 25, 2019 well how i solve this problem ? sorry for bad englishYou would have to update the source code. It doesn't look like an issue because it's catching the exception. You can just ignore it really. Sent from my ONEPLUS A5010 using Tapatalk The developer of the Battlefield Admin Control Panel (BFACP) For BFACP support please post in the BFACP topic linked above. Do not contact me via PM on the forums for help with procon. Please make a topic for it. Only PM's I will accept will revolve around any website issues. Link to comment
Plugin Developer maxdralle Posted November 25, 2019 Plugin Developer Share Posted November 25, 2019 it looks like linsane limits have no permission to compile the limit files. Link to comment
B7ackhawk Posted November 26, 2019 Share Posted November 26, 2019 new update have so many bug . i try run old update but it auto update ! any idea how i stop the update Link to comment
Stov3top Posted November 26, 2019 Share Posted November 26, 2019 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. Link to comment
B7ackhawk Posted November 26, 2019 Share Posted November 26, 2019 new update have so many bug . i try run old update but it auto update ! any idea how i stop the update i did but it auto update Link to comment
Administrators Prophet731 Posted November 26, 2019 Author Administrators Share Posted November 26, 2019 new update have so many bug . i try run old update but it auto update ! any idea how i stop the update Disable the auto-updater in the settings, close procon, then copy the old version in. Also what bugs are you talking about? If you don't tell us what they are then they can't be fixed. These bugs are related to procon client only without plugins. So far, I've seen it as stable in the regard. The developer of the Battlefield Admin Control Panel (BFACP) For BFACP support please post in the BFACP topic linked above. Do not contact me via PM on the forums for help with procon. Please make a topic for it. Only PM's I will accept will revolve around any website issues. Link to comment
Timm Posted November 27, 2019 Share Posted November 27, 2019 Today and yesterday updated few Layers (6-7) working good, i will check how they will behave, then, if ok i will update the rest layers. This link still goes to old forum https://prnt.sc/q2n7kv Link to comment
Administrators Prophet731 Posted November 27, 2019 Author Administrators Share Posted November 27, 2019 Today and yesterday updated few Layers (6-7) working good, i will check how they will behave, then, if ok i will update the rest layers. This link still goes to old forum https://prnt.sc/q2n7kv Yeah, forgot to update that :/ Whoops Please let me know if any issues happen. So far I haven't seen any on my testing servers. The developer of the Battlefield Admin Control Panel (BFACP) For BFACP support please post in the BFACP topic linked above. Do not contact me via PM on the forums for help with procon. Please make a topic for it. Only PM's I will accept will revolve around any website issues. Link to comment
Timm Posted December 8, 2019 Share Posted December 8, 2019 Why Russian lang. removed from this version? Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.