News A server update was released on July 20. Server patch notes and downloads are here. Additionally, a client update was released on the same day. Client patch notes are here.
In order to limit the seemingly arbitrary nature of the promotion of official servers, and to avoid confusion and further debates on the qualifications of certain servers over others, the following criteria are now being used to determine whether a server should be listed as official or not:
:edit: The list of changes to the official server listing is as follows.
Now that it's April 2 in Europe, we're going to come clean — we weren't actually acquired by Rockstar. VC:MP is still an independently developed project. (The upshot, though, is that we definitely won't have microtransactions either!)
We do have a big update coming up soon, though. We'll save more extensive details for when it's released. In the meantime, I just wanted to say thanks for bearing with us on April Fools' day.
The old thread can be found in Off-Topic General, and if you haven't already, do consider reading the first letter of each paragraph.
Have you edited the wiki lately?
As developers, a lot of our time is spent adding features to and fixing issues in the client and server. Unfortunately, a lot of time is not spent by us creating comprehensive documentation of what we add to things like our wiki. Although some parts of the wiki are nicely written, there are entire blocks of Squirrel functions, Squirrel events, and other pages which aren't written, or written less than optimally.
We'd like to see scripters and players contribute more to the wiki to help it become a better resource for new and veteran scripters alike. In accordance with that, we're going to be rewarding contributors with a forum badge that looks like this:
As a small token of appreciation and recognition.
Badged contributors are recognized for making consistent and high-quality revisions to the wiki. If you think you've made a sufficient number of good edits to the wiki, feel free to poke me if you want to receive a badge. Alternatively, just make a bunch of high-quality edits and let me know if you think you've done a good enough job, and I'll either award you a badge or let you know what you could do better.
The inaugural wiki contributors on the forum are:
Their contribution histories have been linked to provide examples of what good wiki editing looks like.
For anyone just starting to edit the wiki extensively, please read these quick contribution guidelines:
Announcing the 0.4 Release Candidate
Posted by Stormeus, on October 6th, 2014, 10:04 PM (1,567 views)
After many successful rounds of private and public beta testing, the VC:MP Development Team is proud to announce the release of the 0.4 Release Candidate.
This is more representative of a final product, and by releasing the server to the public we can collect a significant amount of information regarding bugs and issues that may exist in the server or client. Allowing the community to do whatever they please with the server would be much more productive than simply producing public beta scripts and testing them, as we cannot account for every possible scenario a scripter may want to attempt in 0.4.
Moreover, by releasing the server for scripters to test and develop on, the transition from R2 to 0.4 will be seamless and much smoother, as server owners will more likely be prepared to adopt a completely new version of VC:MP.
Notes on RC Release
Releasing the server as a near-final product for bughunting serves to help scripters become ready for the switch to a final 0.4 release and for bug finding purposes. While this does signal a closer approach to a final release, it is not, by any stretch of the imagination, a polished product we believe should be fully representative of our efforts. Once we feel 0.4 is ready for full release, we will make another announcement and spread the word.
VC:MP 0.4 Client
Note: Clients/browsers from Public Beta 3 will also work with this server beta, and will automatically update as needed, but it is recommended to use the installer for newer and updated browser functionality.
Windows Server (x86)
Windows Server (x64)
Linux Server (x86)
Linux Server (x64)
A list of functions and callbacks can be found on the VC:MP Wiki:
Bug and Crash Reports
Like previous public betas, bugs and crashes can be reported on the forum. However, we also have a new bugtracker at http://bugz.maxorator.com which can be used to report and track bugs in both the server and client as well.
Bug reports filed on the forum will receive responses, but will also be filed on the new bugtracker as well.
Refer to the Reporting Bugs and Crashes thread (linked) for further information and instructions.
As explained in the Bugs and Crashes announcement, we now have a small dashboard for tracking client crashes on 0.4. It isn't really anything major, but it does hold us more accountable for crashes in that there's less of an excuse for us not being aware of them.
What does this mean for you?
Hopefully, nothing other than less crashes.
A companion update has been pushed to allow us to have these crashes reported to our server, which means any crashes that would be logged by VC:MP before are now just being sent to us automatically anyway.
The information we collect consists of the address in memory at which the crash occurred and the log that has already been saved to your disk. Nothing identifiable is intentionally included; we do not include your IP address in our stored metadata. The most identifiable information would probably be your Windows username in the crash logs, if you have any DLLs loaded from your user profile's folder (including VC:MP if you installed to the default installation directory, which is recommended).
I oppose the NSA and please stop destroying my privacy rights.
If you'd like to opt out of this program, go in-game and type /setconfig game_reportcrashes 0 or open your vcmp_config.txt file (which can be located at C:\Users\USERNAME\AppData\Roaming\VCMP\04beta) and add the line game_reportcrashes 0 if it doesn't already exist.
Please note that this program is opt-in by default.
With the 0.3 masterlist now effectively shut down, the old forums have been relocated from their old server to our current web servers on a special archive site:
An archive of the forums from 2007 to 2011 has also been restored from backups on the old server. Posts between 2011 and 2012 that were lost in the account breach could not be recovered.
These forums are completely read-only for all non-developer users (including beta testers). Registrations have been disabled, and functionality such as changing avatars, sending messages, posting, etc. is unavailable. The only other changes made were upgrades to the forum software, so all posts and topics are as they appeared when the backups were made.
Phasing out VC:MP 0.3 and its masterlist
Thanks to bakasan generously reprovisioning access to the original VC:MP web server, we are beginning to phase out VC:MP 0.3 and its masterlist.
As of this posting, vicecitymultiplayer.com redirects to our new website at vc-mp.org, and is marked as a "permanent" redirect in order to make it clear to search engines that this is our new address. This is intended to encourage users to begin using 0.4 over 0.3.
We will also be launching a number of locked dummy servers to show users browsing the 0.3 masterlist that we are in the process of shutting it down, and warning them and server owners to transition to 0.4 immediately.
On Friday, May 1, the VC:MP 0.3 masterlist will be shut down. No new servers will be allowed to announce to it. No existing servers will appear to users trying to access the masterlist. Anyone who wishes to continue playing on 0.3 after the masterlist shutdown may do so by adding servers to their favorites list and accessing them there. However, no 0.3 servers may advertise on this forum, and no official 0.3 server builds will be provided on our website or the ModDB downloads section.
After May 1, we may begin moving the old forum and other data onto our new server here. After that point, it's up to bakasan to decide what he wants to do with the legacy web server.
The masterlist was offline for about 30 minutes, starting around 23:00 GMT. This was caused by an unsmooth transition from SQLite to MySQL. During this time period, the masterlist would return no or malformed data, which would, at times, crash the browser due to unexpected results.
This issue appears to have been resolved, and servers should disappear at random less often, if at all. If this is still an ongoing issue, please report it immediately.