vMenu is a custom server sided trainer/menu, built using a custom version of NativeUI. It has full permissions support, so the server owner can decide who's allowed to do what.
Full Changelog: https://github.com/TomGrobbe/vMenu/compare/v3.6.0...v3.6.2
Full Changelog: https://github.com/TomGrobbe/vMenu/compare/v3.6.0...v3.6.1-pre
Thanks for all the community provided pull requests ❤️! Special thanks to everyone who helped test this release, and to XdGoldenTiger for doing a lot of community PR reviews and merges!
sv_enforceGameBuild 2944
)(This is a known issue with lower game builds. Will there be a proper fix? Maybe. Not had time to work on a fix that has a better workaround)
This update contains mainly bug fixes, some small new features. The latest DLC vehicles, peds and weapons should now also be included.
vMenu.VehicleOptions.DestroyEngine
, default for builtin.everyone
: allow
. Allows the player to destroy their engine in the Vehicle Options menu, from the Vehicle Options.vMenu.PersonalVehicle.ToggleStance
, default for builtin.everyone
: allow
. Allows the player to toggle vehicle stance (for supported vehicles only), from the Personal Vehicle menu.builtin.everyone
:
vMenu.WeaponOptions.HazardCan
vMenu.WeaponOptions.EMPLauncher
vMenu.WeaponOptions.HeavyRifle
vMenu.WeaponOptions.FertilizerCan
vMenu.WeaponOptions.StunGunMP
vMenu.WeaponOptions.PrecisionRifle
vMenu.WeaponOptions.TacticalRifle
vMenu.WeaponOptions.PistolXM3
vMenu.WeaponOptions.CandyCane
vMenu.WeaponOptions.RailgunXM3
vMenu.WeaponOptions.AcidPackage
vMenu.WeaponOptions.TecPistol
New setting keep_player_head_props
: Sets whether or not players can lose their head props when they are hit/pushed.
Default setting:
setr keep_player_head_props true
Possible Values:
true
Props will stay on player (default vMenu and GTA Online behavior)false
vMenu will not touch this feature, by default this means that head props will fall off when the player is hit, which is the default behavior for GTA V Single Player peds.New setting vmenu_using_chameleon_colours
: Allows the use of chameleon colors for supported vehicles.
Default setting:
setr vmenu_using_chameleon_colours false
Important: You must be streaming the chameleon colours in order for this to function properly (if the current DLC version of your server does not provide them already).
Possible Values:
true
Enable the chameleon colour vehicle paints category in the primary colours menu.false
chamelon colors will not be available in the menu.Here's a list of all the changes in this update.
STREAMER216
name typo. (PR #306 By MichaelCoding25).Thanks for all the community provided pull requests ❤️! It's great to see that people are still interested in keeping this resource up to date. This update contains mainly bug fixes and performance improvements, as well as the latest DLC vehicles.
vmenu_enable_snow
convar to set the default value)vmenu_disable_player_stats_setup
convar).vMenu.WeaponOptions.CeramicPistol
vMenu.WeaponOptions.NavyRevolver
vMenu.WeaponOptions.PericoPistol
vMenu.WeaponOptions.MilitaryRifle
vMenu.WeaponOptions.CombatShotgun
vMenu.MiscSettings.EntitySpawner
(moderators only by default)vmenu_handle_invisibility
to prevent vMenu from setting the player's invisibility every frame. Useful if you have other resources that want to override vMenu's player invisibility option.vmenu_disable_player_stats_setup
to prevent vMenu from setting any player stats like stamina, shooting, driving ability, etc.vmenu_enable_snow
to manually enable snow on the ground without having the 'xmas' weather type selected.Ignore this part if you've already upgraded to v3.3.0-pre, skip to the Changes (summary) section
SQLite support has been dropped. This caused too many crashes and was completely incompatible with recent (Linux) FXServer artifacts.
The new ban system uses the default server side storage built in to FXServer. To migrate (copy) your old vmenu_bans.db
or bans.json
file, follow the following steps. If you don't have a vmenu_bans.db
file, and only a bans.json
file skip to step 2.
vmenu_bans.db
file to here, and place the bans.json
file you get here: /resources/vMenu/bans.json
vmenuserver migrate
in the server console. This may take some time depending on the amount of bans you have stored. ONLY RUN THIS COMMAND ONCE, OTHERWISE YOUR BANS WILL BE DUPLICATED
bans.json
and vmenu_bans.db
files, as you'll no longer need them.If you haven't updated to v3.3.0-pre yet, read this part as well before updating to v3.3.1
weapon_components
) in the addons.json
file.Removed options:
vmenu_allow_random_blackout
This feature has been removed.vmenu_smooth_time_transitions
This feature has been removed.vmenu_bans_database_filepath
All SQLite/bans.json options have been removed.vmenu_bans_use_database
All SQLite/bans.json options have been removed.Added options:
vmenu_blackout_enabled
This allows you to set the (default) state for blackout mode.vmenu_sync_to_machine_time
Allows you to sync the time to the server's real system time (the custom in-game hour duration setting will be ignored if this is enabled and you won't be able to change the time manually).vmenu_weather_change_duration
Allows you to configure how long weather changes take.Changed/renamed options:
vmenu_default_time_hour
has been renamed to vmenu_current_hour
vmenu_default_time_min
has been renamed to vmenu_current_minute
vmenu_default_weather
has been renamed to vmenu_current_weather
A new section has been added for weapon_components
in which you can add the names of addon (streamed) weapon components, note that this is untested. They will automatically be matched for compatible weapons and appear as components which you can toggle in the weapon options menu.
SQLite support has been dropped. This caused too many crashes and was completely incompatible with recent (Linux) FXServer artifacts.
The new ban system uses the default server side storage built in to FXServer. To migrate (copy) your old vmenu_bans.db
or bans.json
file, follow the following steps. If you don't have a vmenu_bans.db
file, and only a bans.json
file skip to step 2.
vmenu_bans.db
file to here, and place the bans.json
file you get here: /resources/vMenu/bans.json
vmenuserver migrate
in the server console. This may take some time depending on the amount of bans you have stored. ONLY RUN THIS COMMAND ONCE, OTHERWISE YOUR BANS WILL BE DUPLICATED
bans.json
and vmenu_bans.db
files, as you'll no longer need them.weapon_components
) in the addons.json
file.Removed options:
vmenu_allow_random_blackout
This feature has been removed.vmenu_smooth_time_transitions
This feature has been removed.vmenu_bans_database_filepath
All SQLite/bans.json options have been removed.vmenu_bans_use_database
All SQLite/bans.json options have been removed.Added options:
vmenu_blackout_enabled
This allows you to set the (default) state for blackout mode.vmenu_sync_to_machine_time
Allows you to sync the time to the server's real system time (the custom in-game hour duration setting will be ignored if this is enabled and you won't be able to change the time manually).vmenu_weather_change_duration
Allows you to configure how long weather changes take.Changed/renamed options:
vmenu_default_time_hour
has been renamed to vmenu_current_hour
vmenu_default_time_min
has been renamed to vmenu_current_minute
vmenu_default_weather
has been renamed to vmenu_current_weather
A new section has been added for weapon_components
in which you can add the names of addon (streamed) weapon components, note that this is untested. They will automatically be matched for compatible weapons and appear as components which you can toggle in the weapon options menu.
vMenu version v3.2.1
Note, they don't do anything yet.
Nothing major changed, just updated the dependencies and switched to fxmanifest.lua
instead of __resource.lua
.
And cleaned up some code.
And removed the feature where your ped would keep it's head gear on while in a vehicle, this apparently caused sync issues for other players whenever you got out of the vehicle.