This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
and i am sure its not internet problem.Sounds like a firewall issue, since on the picture it seems like it failed to get the public beta server info too.
I'm still worried that someone will create an asi mod to hack VC:MP.
CLEO mods, however, can still be loaded in by whitelisting CLEO.
I tried in the last public beta test (2) to load the cleo.asi and it didn't work.
Wondering if it really works now.
Steam EXE is not the same as 1.1 EXE. 0.4 will support 1.0 and Steam versions, but not 1.1. To go into more technical details, there are separate VC:MP DLLs compiled for the 1.0 and Steam versions, and the launcher will decide which one to use based on which executable the user has. Steam version support does not require any actual source code changes to VC:MP, instead the source code that is compatible with Steam version is automatically generated from the base VC:MP source code based on address differences in the executables and a list of patches for a few parts that cannot be converted just by adjusting memory addresses.1. I heard 0.4 will be supporting the steam version. Will it be supporting the 1.1 executable, or just putting the 1.0 executable in the folder and launching from it as a workaround?The Steam EXE itself will be supported.Quote1.1. If it's supporting the actual 1.1 exe, will it still support the 1.0 exe? That sounds like double the work.The 1.0 EXE will also continue to be supported; maxorator would be better able to explain how much work it was since was entirely his design.