04.10.2011, 19:28
(
Last edited by PowerPC603; 06/10/2011 at 05:13 PM.
)
Quote:
|
HI , I have a good question, it is possible When a player quit from server his cars remain loaded ??
|
On top of the script, you\'ll find:
pawn Code:
// Setting this to "true" will load all vehicles assigned to houses when the filterscript loads
// Setting this to "false" will load the vehicles assigned to a house when the house-owner logs in (they\'ll also disappear when he logs out)
// Recommended setting for popular servers (with alot of players): "false"
// In popular servers, the amount of cars could go over the samp-limit (2000), bugging everything when all cars stay loaded
// even when the owner of the vehicle is offline
new bool:LoadCarsDuringFSInit = false;
The comments are a bit vague, but it means:
- Load all house-vehicles during initialization of the script (while the houses are being loaded) and spawn them
- Also keep them loaded when players logout
The comments explain what could happen if you use this feature.
Picture this:
- you have 500 players (accounts) on your server (which is not much)
- all players have 2 houses (which also isn\'t much, I have this set to 20 on my test-server)
- each house has 5 vehicles assigned to it (max per house would be 10 for a level 10 house, so also not that much)
Then the total amount of cars = 500 players * 2 houses * 5 vehicles = 5000 cars.
BUT the samp-limit is only 2000, and cannot be expanded.
So, players have bought 3000 cars too many, which never appear.
Guess what will happen to your player-base?
They will leave because they think your server is bugged (they bought a car but never got to drive it).
So, use that setting with extreme caution.
It\'s only recommended for local servers, or servers with only a few players (less than 100).
Or you can create static houses with a slot-count of 2 (fixed amount of carslots) and only allow one house per player.
Then it\'s easier to have more than 100 players.


