- Welcome to Vice City: Multiplayer.
Recent posts
#1
Servers / WTVC
Last post by NASCAR 2025 - Oct 28, 2025, 03:37 PM
[size=18]🚗 WELCOME TO VICECITY (WTVC) – CAR SHOW & DM / RP SERVER LAUNCH 🚗[/size]
THE SERVER IS HERE!
After seeing countless servers with endless car shops and zero progression, we're proud to officially launch our Welcome to ViceCity – Car Show / DM / RP server — fully structured, action-packed, and designed to give every player a real progression path. No more pointless word bans — we're not your parents.
SERVER FEATURES & ACCESS
• Grid-based leveling system and structured car ownership — no more just buying the best cars instantly.
• Minimal cars for sale: everything requires effort, grinding, and progression.
• On our Discord, you can buy cars, customize them, and upgrade your rides — just speak to the admins to get started.
• Scheduled Car Meets every day at 11:00 AM & 11:00 PM Pakistan Time — show off your cars, socialize, and compete for top spots.
• Tons of ways to make money: participate in events, DM battles, RP scenarios, and special server challenges.
• Server drops this week — get ready to join, compete, and grind your way to the top.
RULES & STRUCTURE
• This server is a mix of car shows, DM zones, and RP areas — respect each mode and keep the experience fun for everyone.
• Every player has a progression path: earn levels, unlock perks, and upgrade cars based on effort and achievements.
• Cheating, trolling, or breaking the RP/DM rules will result in warnings, kicks, or bans.
• Cars, upgrades, and achievements are yours to keep as long as you play by the rules — violators lose everything.
• No more word bans — freedom to chat, RP, and grind without unnecessary restrictions.
WHY YOU SHOULD JOIN
• Experience a fully structured ViceCity server with long-term progression.
• Get involved in car shows, DM action, RP events, and community challenges.
• Forget servers with no structure — this one rewards skill, time, and dedication.
• Be part of a community where grinding, strategy, and competition actually matter.
HOW TO JOIN
Click the invite link to join our Discord: https://discord.gg/DYF56y89dM[/url
]
On Discord, you can buy cars, customize them, and prepare for events — speak directly with the admins.
Check your level system dashboard and start grinding for perks, money, and upgrades.
Participate in events, complete challenges, and show off your cars!
Commitment matters — this server rewards effort and dedication.
#2
Weapon Showroom / DEWPACK #1 (vcmp guns, skins a...
Last post by NASCAR 2025 - Oct 28, 2025, 12:32 PM'M DROPPING MY FIRST MOD PACK FOR Y'ALL!
Hey everyone,
I've put together a mod pack full of skins, guns and cars (plus some beta weapons included) that I have no use for — but maybe some of you will.
Download here
Please feel free to:
hope you enjoy it!
Hey everyone,
I've put together a mod pack full of skins, guns and cars (plus some beta weapons included) that I have no use for — but maybe some of you will.
Download here
Please feel free to:
- Try it out on your server
- Let me know what works and what doesn't
- Report any bugs or missing assets
hope you enjoy it!
#3
General Discussion / Re: MEGAMIND'S VCMP BROWSER
Last post by MEGAMIND - Oct 27, 2025, 03:33 PM
Features
- VOIP bug fixed (No voice was being heard)
- CEF browser bug fixed (Updated plugin)
- Theme changer store bug fixed (User applied theme saves now)
Update your browsers to stable release (Recomended)
Note: Windows 7 users can download it from website manually
Those who have the browser already installed will get a update automatically, those who are new to this browser can download and install the latest update
#4
Script Showroom / Re: Squirrel Dependency Inject...
Last post by PSL - Oct 27, 2025, 05:42 AMIf class B extends Sqoin (i.e. class B inherits from class Sqoin), then inside class B you can directly use this.get(...) to get all injected modules
This usage, achieved by "inheriting the Sqoin class," is equivalent to giving Class B a direct access to the dependency repository. Class B automatically inherits all of Sqoin's dependency management capabilities, such as obtaining singletons and factory instances, and passing dynamic parameters (this.get("UserService", {id = 1})). It's like moving the dependency injection "toolbox" directly into Class B, making it more convenient to use.
Code Select
class B extends Sqoin {
constructor() {
local logger = get("Logger");
logger.log("B");
}
}
This usage, achieved by "inheriting the Sqoin class," is equivalent to giving Class B a direct access to the dependency repository. Class B automatically inherits all of Sqoin's dependency management capabilities, such as obtaining singletons and factory instances, and passing dynamic parameters (this.get("UserService", {id = 1})). It's like moving the dependency injection "toolbox" directly into Class B, making it more convenient to use.
#5
Script Showroom / Re: Squirrel Dependency Inject...
Last post by PSL - Oct 27, 2025, 05:26 AMCurrently implementing a flexible injection method of default parameters + dynamic parameters.
When registering a dependency, you can set a set of default configurations (for example, presetting the default output format for a logging tool); and when using the dependency, you can pass in new parameters at any time (for example, temporarily changing the output format to debug mode).
Dynamically passed parameters automatically override the default configuration, preserving the default settings while also adapting to temporary requirements in different scenarios. For example, you might use a regular database when registering a user service, but dynamically pass parameters to a test database during a subsequent call without having to modify the original registration rules. This provides flexibility and convenience.
This code demonstrates the "default parameter + dynamic parameter" injection effect in the factory pattern:
1. When registering a Logger as a factory, default parameters are set via {id = 1}, serving as the base configuration for instance creation.
2. When logger1 is first retrieved without parameters, a Logger instance is created using the default parameters id = 1.
3. When logger2 is retrieved a second time with {id = 2}, the dynamic parameters override the default values, creating a new instance with id = 2.
Because of the factory pattern, each get call generates a new instance, and dynamic parameters take effect in real time, making it suitable for scenarios requiring differently configured instances.
When registering a dependency, you can set a set of default configurations (for example, presetting the default output format for a logging tool); and when using the dependency, you can pass in new parameters at any time (for example, temporarily changing the output format to debug mode).
Dynamically passed parameters automatically override the default configuration, preserving the default settings while also adapting to temporary requirements in different scenarios. For example, you might use a regular database when registering a user service, but dynamically pass parameters to a test database during a subsequent call without having to modify the original registration rules. This provides flexibility and convenience.
Code Select
module.factory("Logger", function(sqoin, args) {
return Logger(args.id);
}, {
id = 1
});
local logger1 = Sqoin.get("Logger");
local logger2 = Sqoin.get("Logger", {
id = 2
});
This code demonstrates the "default parameter + dynamic parameter" injection effect in the factory pattern:
1. When registering a Logger as a factory, default parameters are set via {id = 1}, serving as the base configuration for instance creation.
2. When logger1 is first retrieved without parameters, a Logger instance is created using the default parameters id = 1.
3. When logger2 is retrieved a second time with {id = 2}, the dynamic parameters override the default values, creating a new instance with id = 2.
Because of the factory pattern, each get call generates a new instance, and dynamic parameters take effect in real time, making it suitable for scenarios requiring differently configured instances.
#6
Script Showroom / Re: Squirrel Dependency Inject...
Last post by PSL - Oct 27, 2025, 03:11 AMhttps://github.com/leitingzi/vcmp_server.git
My repository contains the core code for dependency injection and a test server that can be run.
My repository contains the core code for dependency injection and a test server that can be run.
#7
Script Showroom / Squirrel Dependency Injection ...
Last post by PSL - Oct 27, 2025, 03:07 AMThis Squirrel code implements a simple dependency injection (DI) framework with the following core features:
1. Provides a Module class for defining dependency bindings, supporting two binding types: single (singleton) and factory (factory). Register types and corresponding providers through the single() and factory() methods respectively.
2. Sqoin serves as the framework entry point and provides singleton context access (getInstance()), module loading (loadModules()), and instance acquisition (get()) functions through static methods.
3. SqoinContext is the core of the context, responsible for managing modules, storing singleton and factory registration information, and obtaining instances by type through the get() method (the singleton is created and cached by the provider when it is first obtained, and the factory creates a new instance each time it is called)
The overall dependency registration and resolution mechanism is implemented, which can be used to manage object dependencies in the server.
This Squirrel code defines three business classes, forming a simple user information processing chain:
1. Logger class: Provides basic logging functionality, printing messages via the log method.
2. UserRepository class: Responsible for acquiring user data. Its constructor relies on Logger. It uses the getUser method to query user information based on ID and log it.
3. UserService class: Serves as the business service layer, relying on UserRepository and Logger. It encapsulates the user information acquisition process via the getUserInfo method, logging before calling repository layer methods.
The three collaborate through dependencies, embodying the layered design concept (log component, data access layer, business service layer), and can be combined with the dependency injection framework to manage dependencies.
This Squirrel code defines a dependency injection module userModule, which is used to configure the instance creation rules of each business class:
1. The configuration function is passed to the Module constructor, and the Logger and UserRepository are registered as singletons using the single method:
1. The Logger instance is created directly using the no-argument constructor.
2. The UserRepository depends on the Logger and constructs itself after obtaining the Logger instance through the dependency injection container.
2. The UserService is registered as a factory using the factory method: Each time a new UserService is constructed, the container retrieves the UserRepository and Logger instances.
This module declares dependencies and provides instance creation and dependency management rules for the previously defined Logger, UserRepository, and UserService, allowing them to be loaded and used by the injection framework.
This Squirrel code example demonstrates the use of the dependency injection framework:
1. First, the previously defined userModule is added to the modules array. Sqoin.loadModules is used to load the module, completing dependency registration.
2. Sqoin.get("UserService") is called twice to obtain service instances (because UserService is registered as a factory, two different instances are generated).
3. The getUserInfo method is called on each UserService instance, passing in different IDs (123 and 456) to retrieve user information.
Running this code triggers logging and user data querying, demonstrating how the dependency injection framework manages object creation and dependency propagation. It also demonstrates the factory pattern's characteristic of generating a new instance each time a request is made.
1. Provides a Module class for defining dependency bindings, supporting two binding types: single (singleton) and factory (factory). Register types and corresponding providers through the single() and factory() methods respectively.
2. Sqoin serves as the framework entry point and provides singleton context access (getInstance()), module loading (loadModules()), and instance acquisition (get()) functions through static methods.
3. SqoinContext is the core of the context, responsible for managing modules, storing singleton and factory registration information, and obtaining instances by type through the get() method (the singleton is created and cached by the provider when it is first obtained, and the factory creates a new instance each time it is called)
The overall dependency registration and resolution mechanism is implemented, which can be used to manage object dependencies in the server.
Code Select
class Logger {
function log(message) {
print("Log: " + message);
}
}
class UserRepository {
logger = null;
constructor(logger) {
this.logger = logger;
}
function getUser(id) {
this.logger.log("Getting user with id: " + id);
return {
id = id,
name = "User " + id
};
}
}
class UserService {
repo = null;
logger = null;
constructor(repo, logger) {
this.repo = repo;
this.logger = logger;
}
function getUserInfo(id) {
this.logger.log("Fetching user info");
return this.repo.getUser(id);
}
}
This Squirrel code defines three business classes, forming a simple user information processing chain:
1. Logger class: Provides basic logging functionality, printing messages via the log method.
2. UserRepository class: Responsible for acquiring user data. Its constructor relies on Logger. It uses the getUser method to query user information based on ID and log it.
3. UserService class: Serves as the business service layer, relying on UserRepository and Logger. It encapsulates the user information acquisition process via the getUserInfo method, logging before calling repository layer methods.
The three collaborate through dependencies, embodying the layered design concept (log component, data access layer, business service layer), and can be combined with the dependency injection framework to manage dependencies.
Code Select
local userModule = Module(function(module) {
module.single("Logger", function(sqoin) {
return Logger();
});
module.single("UserRepository", function(sqoin) {
return UserRepository(sqoin.get("Logger"));
});
module.factory("UserService", function(sqoin) {
return UserService(sqoin.get("UserRepository"), sqoin.get("Logger"));
});
});
This Squirrel code defines a dependency injection module userModule, which is used to configure the instance creation rules of each business class:
1. The configuration function is passed to the Module constructor, and the Logger and UserRepository are registered as singletons using the single method:
1. The Logger instance is created directly using the no-argument constructor.
2. The UserRepository depends on the Logger and constructs itself after obtaining the Logger instance through the dependency injection container.
2. The UserService is registered as a factory using the factory method: Each time a new UserService is constructed, the container retrieves the UserRepository and Logger instances.
This module declares dependencies and provides instance creation and dependency management rules for the previously defined Logger, UserRepository, and UserService, allowing them to be loaded and used by the injection framework.
Code Select
local modules = [userModule];
Sqoin.loadModules(modules);
local userService1 = Sqoin.get("UserService");
local userService2 = Sqoin.get("UserService");
userService1.getUserInfo(123);
userService2.getUserInfo(456);
This Squirrel code example demonstrates the use of the dependency injection framework:
1. First, the previously defined userModule is added to the modules array. Sqoin.loadModules is used to load the module, completing dependency registration.
2. Sqoin.get("UserService") is called twice to obtain service instances (because UserService is registered as a factory, two different instances are generated).
3. The getUserInfo method is called on each UserService instance, passing in different IDs (123 and 456) to retrieve user information.
Running this code triggers logging and user data querying, demonstrating how the dependency injection framework manages object creation and dependency propagation. It also demonstrates the factory pattern's characteristic of generating a new instance each time a request is made.
#8
Support / Re: any built-in Solution?
Last post by (vG)DesTroYeR^ - Oct 26, 2025, 10:38 PMQuote from: vitovc on Oct 26, 2025, 06:36 PMflooding PlaySound(id) some blank sound would help to stop current sound (in theory, not tested)
my friend gave me empty sound(id 255), but i will give it a try, i dont think it would work unless it is a flag which can be customizable
#9
Videos & Screenshots / HerKulano : The Legend Who Ref...
Last post by herqules - Oct 26, 2025, 10:33 PM #10
Support / Re: any built-in Solution?
Last post by vitovc - Oct 26, 2025, 06:36 PMflooding PlaySound(id) some blank sound would help to stop current sound (in theory, not tested)