Installations

Remember that this resource has verified DMCA protection, and its illegal use or distribution could imply a claim for protection of Title 17 of Chapter 512 (c) (3) of the Digital Millennium Copyright Act

STEP 1 - Dependencies

It is important to use the dependencies that are indicated in this step, do not use others, otherwise you will receive critical errors
For the weather to behave normally, we must choose between vSync or cd_easytime, even if you don't use either, nothing will happen either, it just won't change the weather inside the homes
Do not forget to install any of these dependencies, otherwise the resource will not work correctly, make sure you have started all of them correctly

STEP 2 - Start order

It is important to put the resources in the correct order, below es_extened but above the other scripts
In order for the resource to start correctly and not receive any errors, we must start the resources in the following order
1
ensure qs-housing
2
ensure k4mb1shellstarter
3
ensure PolyZone
4
ensure meta_libs
5
ensure interact-sound

STEP 3 - Database

Before placing our [sql] file, we will remove the old tables similar to qs-housing from our server, so as not to cause critical database errors
To do this, we will execute the following code in our database
DROP TABLE IF EXISTS player_houses;
DROP TABLE IF EXISTS houselocations;
This code is mandatory to run before starting to install the new database
Do not start the resource without first having installed the complete database, if you start the resource in the database, you will get critical errors
Housing database
1
CREATE TABLE `houselocations` (
2
`name` varchar(255) NOT NULL,
3
`label` varchar(255) DEFAULT NULL,
4
`coords` text DEFAULT NULL,
5
`owned` tinyint(2) DEFAULT NULL,
6
`price` int(11) DEFAULT NULL,
7
`tier` tinyint(2) DEFAULT NULL,
8
`garage` text DEFAULT NULL,
9
`creator` varchar(50) DEFAULT NULL,
10
`mlo` text DEFAULT NULL,
11
`ipl` text DEFAULT NULL,
12
PRIMARY KEY (`name`)
13
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
14
15
CREATE TABLE `player_houses` (
16
`house` varchar(50) NOT NULL,
17
`identifier` varchar(50) DEFAULT NULL,
18
`insideId` varchar(50) DEFAULT NULL,
19
`keyholders` text DEFAULT NULL,
20
`decorations` text DEFAULT NULL,
21
`stash` text DEFAULT NULL,
22
`outfit` text DEFAULT NULL,
23
`logout` text DEFAULT NULL,
24
`charge` text DEFAULT NULL,
25
`credit` varchar(50) DEFAULT NULL,
26
`creditPrice` varchar(50) DEFAULT NULL,
27
PRIMARY KEY (`house`)
28
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;
29
30
ALTER TABLE `users` ADD `inside` VARCHAR(100);
31
ALTER TABLE `player_houses` ADD `decorateStash` TEXT COLLATE 'utf8mb4_general_ci';
32
33
INSERT INTO `addon_inventory` (name, label, shared) VALUES
34
('property', 'Property', 0)
35
;
36
37
INSERT INTO `addon_account` (name, label, shared) VALUES
38
('property', 'Property', 0)
39
;
40
41
INSERT INTO `datastore` (name, label, shared) VALUES
42
('property', 'Property', 0)
43
;
44
45
INSERT INTO `addon_account` (name, label, shared) VALUES
46
('society_realestate','Real estate agent',1)
47
;
48
49
INSERT INTO `jobs` (name, label) VALUES
50
('realestate','Real estate agent')
51
;
52
53
INSERT INTO `job_grades` (job_name, grade, name, label, salary, skin_male, skin_female) VALUES
54
('realestate',0,'rookie','Rookie',10,'{}','{}'),
55
('realestate',1,'seller','Seller',25,'{}','{}'),
56
('realestate',2,'manager','Manager',40,'{}','{}'),
57
('realestate',3,'boss','Boss',0,'{}','{}')
58
;

STEP 4 - Garages

Quasar Housing can be compatible with any garage for which a Housing function has been created, therefore, not all of them are compatible by default, here we will attach the list of garages compatible with qs-housing by default
If you have a garage with such necessary events, don't worry, you can add it manually with the following settings
We do not support garage systems, as each creator must formulate their own events to support it. If you don't want to use the Housing Garage, you can skip it
Among the garages verified to work with qs-housing, we find qs-garages, qb-garages, cd_garages and jg_adavencedgarages
Garages
Download links and stores
qs-garages
qb-garages
cd_garages
jg_adavencedgarages

STEP 5 - Stashes

Inside config.lua we will find an exclusive configuration for the Stash and your inventory system, here we can choose between several default inventories simply by modifying Config.StashType to the system that we want, everything is noted next to the configuration
If you don't have basic Lua and ESX skills please set only one default inventory and avoid using the following options below
In case we want to add furniture with stash, we will have a basic configuration where we will add the prop name to add a small stash in Config.ObjectStash, we can see the furniture corresponding to this configuration inside config_furniture.lua
You can configure more, but these are included by default

STEP 6 - Wardrobes

Quasar Housing has a basic wardrobe system, which will allow you to place a wardrobe that triggers an external event to open your outfits
By default you will have some options, but you can choose a custom one with the event below and putting Config.OutfitType in the custom option
We can also configure some furniture to bring a default wardrobe in the Config.ObjectWardrobe, we can guide ourselves and obtain the prop name from config_furniture.lua
You can configure more, but these are included by default
Clothings
Download links and stores
fivem-appearance
qb-clothing
rcore_clothes