Topics

[Custom sound files can now be played using PlaySound.]

The first client update of 2016 has been released for 04rel003.

• Custom sound files can now be played using PlaySound.
  
  Server owners: to use this feature, add .wav files to store/sounds/. Each sound added will have an ID starting with 50000 which can be played through PlaySound as usual. Filenames should be in the format of sID_NAME.wav where ID starts with 50000.
  
  No server update is necessary for this feature.

• Fixed players being able to gain immunity to gunfire by rapidly switching in and out of first-person view.
• Fixed players occasionally not seeing shots from behind them until they saw the player shooting them.
• Fixed players taking critical damage and losing all armour when being shot in the arms and legs.
• Attempted a more aggressive fix for slide glitching.
  
  • Fixed players sliding aggressively when transitioning from crouched to standing up.
  • Attempted to reduce slide duration when a player is moving while standing.
  • Shotgun timing for remote players should improve as well due to this patch.
• Shots fired by people in first-person should now appear to shoot from the muzzle, and not from behind the player's head.
• Added config option scr_shortmsg. When set to 1, VC:MP will shorten the "screenshot saved" message by only printing the filename, and not the full path.
• Added console shortcuts for jumping to the first and last lines in the scrollback buffer. (HOME and END by default, respectively. Only effective when the console is open.)
• Added config options con_scrollupkey, con_scrolldownkey, con_jumptopkey and con_jumpbottomkey to reconfigure the keys used for scrolling through the console.
• Fixed smoke and shadows being transparent or appearing lighter in screenshots. FRAPS overlays will also appear properly if captured in screenshots.
• Reduced the delay in switching classes on a spawn screen from 1000ms (1sec) to 250ms (0.25sec).

This update will take effect upon reloading the browser.

A client update has been released for 04rel003.

• Fixed a security issue that allowed tampering with UIDs.
• Dying players can no longer use /kill
• Players who took damage recently will no longer have their damage source reset when using /kill
• con_numoflines now has a minimum of 0 instead of 5.
• Fixed a possible issue that caused excessive sliding
• Friendly damage no longer causes players to fall down
• Added a hotkey (F7 by default) that resizes the console by 5 lines. This can be rebound by changing con_resizekey.
• Attempt to fix an issue where shooting a player in the head while they're driving causes the car to jump backward.

This update will take effect upon reloading the browser.

A client update has been released for 04rel003.

• Fixed emergency vehicle lights for non-MVL vehicles.
• Fixed the game freezing when loading the Steam version in fullscreen mode.
• Blocked a first-person quickscope exploit that allowed shooting through walls and being more unhittable.
• Fixed being able to reconnect to servers you were kicked from through the menu.
• Spike strips are now removed when their owner dies, is streamed out, or is too far away.
• FPS is now properly reported when the player is paused.
• Attempts to make checkpoints and spheres more stable.
• Added a new splash screen.

This update will take effect upon reloading the browser.

[IP]

This thread mostly serves as a reference for server owners whose servers may not be appearing on the masterlist. If an IP address that you own is on the list, send me a private message in order to request an unban.

IP		Ban Reason
41.161.115.229		Announcing 0.3 servers to the 0.4 masterlist
123.56.102.103		Spamming the masterlist with dozens of servers to push a political agenda
222.186.46.40		Spamming the masterlist with dozens of locked servers
131.72.136.115:8192		Fake copy of an official server (XE)
89.133.188.253		Using the masterlist as a soapbox to harass people
222.187.221.112		Using the masterlist as a soapbox to harass people
115.42.64.135		Spamming the masterlist with dozens of copies of the same server
92.44.104.167		Copyright infringement
104.248.31.223		Fake copy of an official server (Littlewhitey's)
138.68.81.159:8191		Server owners involved with attacks to other servers
20.193.236.93:8190		Server owners involved with attacks to other servers

• Claiming stolen or plagiarized scripts as your own will result in your threads getting taken down and the loss of posting privileges if it happens repeatedly.
• Accusing other players of having stolen a script and claiming it as their own, without any proof, will result in your posts being taken down and the loss of posting privileges if it happens repeatedly.
• Posting precompiled scripts without accompanying source code is not allowed due to the possibility of distributing malicious code.

These rules will likely be expanded on in the future for quality control purposes.

[Season 4]

Season 4
Credit to [DnA]Ryz for image

http://vu.vrocker-hosting.co.uk/index.php#c20

What is the VCDC?
The Vice City Dueling Championship is an idea that was first devised by [VU]aXXo in 2009. Since then, we have had three successful tournaments with 40 competitors each and it is time for the fourth.

The tournament will consist of three stages: a group stage, a Swiss-style competition with the top two players from each group, and single-elimination quarterfinals/semifinals/finals. After the applications have been closed, groups will be decided by matching players' timezones as closely as possible, so as to make organising matches easy.

Details about how each stage will work will be released in the relevant forum board. This will be an ongoing event, it will not be on a particular day. Matches can be fought at any time, on any VCDC server, as long as an admin is present.

More information is available here.

Who can participate? How do I sign up?
Anyone* can participate! Registration is essentially uncapped as the player limit will be raised as long as the tournament doesn't end up being too complex to administrate.

Register to fight here.

* Known hackers will be rejected.

What prizes are there?
The winner gets the satisfaction of being the best player in the tournament!

A prize pool on Littlewhitey's has been set up as well; players may donate to VCDC_PrizePool in return for acknowledgement on the forum. More information about the prize pool is available in this thread.

https://www.youtube.com/watch?v=QF9Imltkvrw

This is a weird one.

Basically what happened just before this clip is that the player was flying in on a helicopter. As they descended, I started shooting the helicopter. On their screen they were jumping out but on my screen they were still in the helicopter as it blew up.

What ended up happening was the player was incorrectly marked as dead and their body lies on the ground, but they're still able to move around as evidenced by the shadow and the shots on the player causing the dead body to twitch.

No crashes occurred, just this, though I also got accused of hacking (which makes some sense).

A client update has been released for 04rel002.

• Reverted mouse sensitivity options to Public Beta 3 style.
  
  • Removed game_mouse_xsens and game_mouse_ysens
  • Added game_sensitivity, which proportionally affects X and Y sensitivity settings
• Fixed first-person M4 and M60 shots not appearing on other players' screens
• M4 and M60 no longer shake the camera in first person mode
• Pizza Boy can now hold a passenger as well as the driver
• Fixed a race condition in the console that could cause a crash when taking screenshots

This update will take effect upon reloading the browser.

A client update has been released for 04rel002.

• "Start New Game" in the pause menu has been replaced by a reconnect option.

This update will take effect upon reloading the browser.

It's just something I rigged together while bored; a graph of player count over time. There are a few sharp drops in the graph due to server queries occasionally failing, but I plan on fixing that soon.

Timestamps are GMT-5.

http://activity.vicelegends.com/players.svg

[Hash any passwords when registering.]

Because this is still necessary.
Copied from http://vcmp.liberty-unleashed.co.uk/forum/index.php?topic=1663.msg11107#msg11107


Some people have a noteworthy lack of common sense, which prompted me to write this. Let me know if I've missed anything important.


If you are planning on releasing a script, make sure you do the following:

Hash any passwords when registering.
FBS does not hash passwords and stores them in plaintext. Therefore, all FBS-based scripts will also store passwords in plaintext. This is an easy way to get your script removed. Make sure that you are using some sort of password hashing system, such as SHA256 or WHIRLPOOL.

Remove the VCMPServer.exe file.
It's not necessary to add this file. It adds a lot of unnecessary size. It could be out of date. It's useless for Linux servers. It also tends to be infected with viruses. Do yourself a favor; eliminate any risk of being banned and just make life easier for everyone by not including VCMPServer.exe. On that same note, don't include the Linux server either, for the same reasons.

Including server.conf and other files is fine. Just not VCMPServer.exe, or any executable, for that matter.

Verify that the script is working properly.
Take your script, extract it, and start fresh with the latest Squirrel server available. If you are using a database, erase it and start from scratch. Make absolutely sure that all functions and commands are working as they should.

If your script uses a database, make sure that you either add a bare-bones Database file with all unnecessary entries removed, or that you include a file with the CREATE TABLE/INSERT statements that need to be run.

Check the ZIP file for viruses.
Upload your script's ZIP file to http://www.virustotal.com/ and make absolutely sure that there are no viruses. If there are, run a virus scan on your system, because a normal VC:MP server and script will never contain viruses, and you've fucked up somewhere down the road.

This may not apply if your script is set up like an installer which extracts itself, in which case, you should never do that anyway and should simply ZIP up your script.

Upload to a reputable file host.
Do not upload to localized file hosts or hosts with numerous ads and the potential to hijack the browser. http://mega.co.nz, for example, does not show advertisements on the download screen, and will not attempt to show popup/popunder ads or hijack the browser.

If you own your own web server, and can host the file without having to show ads or go through a third-party, then do so (e.g. http://www.vicelegends.com/files/MyScript.zip).

Give attribution in your thread.
If your thread is based on FBS (which it shouldn't be) or VBS, say so. If it is based on Warchiefs, say so. Not granting attribution to a scripter who may have provided the entire base for your modified script will be a major hit to your reputation.

Add what modules you are using.
If your script uses certain modules, including those that come with the Squirrel server, make sure to list them and, optimally, provide links to them. Do not include them in the actual ZIP file, as it is not going to work on both Windows and Linux, and may also be infected with malware.

Fix bugs in your script as they are reported.
Do not leave bugs unchecked; if someone reports a syntax error in a command, fix it, reupload it, and update the link in your original post.

A client update has been released for 04rel002.

• Fixed custom spike strip weapons (logical ID of 80) not actually deploying spike strips and freezing players when fired.
  
  • This fix is a stopgap measure and not a permanent fix. Known issues can be found here. Please don't post any bugs about spike strips other than crashes.
• Fixed a crash caused by possible vehicle model loading failures.
• Fixed a crash caused by trying to make player peds talk if the user has no audio files.
• Fixed a crash caused by trying to set an unstreamed player's alpha.
• Added 0x20 (32 in decimal) as an immunity flag that makes players immune to falling down.
• Fixed the client's maximum server length not matching the server's.
• The scoreboard now shortens excessively long server names.

This update will take effect upon loading the browser or joining a 04rel002 server.

Note: Previous versions of this patch suffered from memory access violation bugs which have now been resolved.

• Spike strips, as custom weapons, rely on weapon sync; timing issues could cause spikes to not appear for some players
• Spike strips only appear to other players when they are in the vicinity of (streamed in with) the player deploying the spike strips and  therefore are not suitable for long ranges.

Do not report any other bugs regarding spike strips other than crashes as we know they're relatively crap.

[Last Server Update]

This is a resource for server owners to have a centralized location for getting the latest server files. This thread will be edited on each server/plugin update to ensure it's up-to-date. If this thread is not updated, message a developer or a moderator who can update it.

Last Server Update
https://forum.vc-mp.org/?topic=8223.0


Linux (64-bit)
https://v04.adtec.ovh/server/VCMP04_server_v34_linux64.zip

Linux (32-bit)
https://v04.adtec.ovh/server/VCMP04_server_v34_linux32.zip

Windows (64-bit)
https://v04.adtec.ovh/server/VCMP04_server_v34_win64.zip

Windows (32-bit)
https://v04.adtec.ovh/server/VCMP04_server_v34_win32.zip

Plugin Pack
https://v04.adtec.ovh/allplugins_04rel006_patch2.7z

Plugins
The plugin packs linked are generally up-to-date, and its contents are updated on every announced plugin update. The Squirrel repository may have more bleeding edge changes from community contributors which can be found here:

https://bitbucket.org/stormeus/0.4-squirrel/downloads

Individual plugins can also be downloaded from each plugin's own page.

Announce: https://bitbucket.org/stormeus/0.4-announce/downloads
server.conf Loader: https://bitbucket.org/stormeus/0.4-confloader/downloads
Hashing support: https://bitbucket.org/stormeus/0.4-hashing-algorithms/downloads
INI support: https://bitbucket.org/stormeus/0.4-iniparser/downloads
MySQL support: https://bitbucket.org/stormeus/0.4-mysql/downloads
Socket support: https://bitbucket.org/stormeus/0.4-sockets/downloads
SQLite support: https://bitbucket.org/stormeus/0.4-sqlite/downloads

Custom weapons that use spike strips as their logical base don't function properly.

Throwing the spike strip causes the player to freeze in place. No spike strip is actually created. IIRC, the weapon does not have a default icon either.

A client update has been released for 04rel002.

• Checkpoint and sphere entry/exit events are now more reliable.
• Fixed a potential issue where running completely through a small enough checkpoint or sphere at a sufficiently low framerate would cause this to not be detected and reported.
• UIDs are now sent with crash reports sent to crashes.vc-mp.org
• Fixed an issue where spectating a player who was in a different interior would render the wrong interior.
• Fixed a logic error that caused snipers in first-person aim to not trigger the aim animation on other players' screens.
• /disconnect no longer triggers an automatic reconnect.

This update will take effect upon loading the browser or joining a 04rel002 server.

[[0.4 | R2] Extremewhiteycity CTFNRPG Deathwaroam City Clan City Server 3030]

A unique script does not guarantee a player base. Imagine a server streaming epileptic music, with players firing Miniguns glued to Linerunners driving around with nitro boost on zero gravity. I'd rather play on the blank game mode.

[0.4 | R2] Extremewhiteycity CTFNRPG Deathwaroam City Clan City Server 3030


Name
[0.4 | R2] Extremewhiteycity CTFNRPG Deathwaroam City Clan City Server 3030

IP
178.62.228.75:8198

Version
1.1

Website
yes

Developer
Stormeus

Admin
Stormeus

Producer
Stormeus

Financer
Stormeus

Burgwer
Stormeus

Shithead
morphine Stormeus morphine

Assistant Shithead
Shadow

Credits
Stormeus


This is a joke, please don't hurt me.

[What does this mean for you?]

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.

[http://crashes.vc-mp.org/]

A tracker for automatically reported client crashes has been set up at http://crashes.vc-mp.org/.

The tracker shows crashes that were able to be reported, so fatal errors that occur before logging can happen (or, if it were to happen, crashes in the logger itself) will not appear.

No personally identifiable information is included on the public facing site; the crash logs themselves are not available to the public, and can only be obtained by developers.

The purpose of this system is to help identify crashes that affect players on 0.4, as well as to have something to look at and be slapped with in order to reduce the frequency of crashes that occur.

If you do not want your crashes automatically reported, use /setconfig game_reportcrashes 0 in-game.

A client update has been released for 04rel002.

• Crash logs are now automatically reported to a central server for analysis.
• Automatic reporting of crashes can be disabled by using /setconfig game_reportcrashes 0

This update will take effect upon loading the browser or joining a 04rel002 server.