Give the players in your server the ability to transfer to their own worlds where they can invite others to explore and roam the world. Grant your players a safe space where they can escape the carnage to relax, explore, and get creative! Players can send invites to other players or send a request to join other players’ worlds! Furthermore, possessing control over who is allowed in their own worlds! Fully server synced with an extensive configuration file that allows integration of multiple different frameworks.
Translatable language file, easy to change language file add your own if needed
Infinite player worlds
Allow players to transfer to their own private Player World, with the ability to invite other players to join them. Or alternatively, join other players’ private worlds!
download hqly_player_worlds and drag and drop into your resources folder
add start hqly_player_worlds to your server.cfg file
edit config.lua
3.1. change permissionType to either ace, command, or none
3.2. change notificationFramework to gtav
follow the specific permissions framework guide found below
QBCore
make sure you have QBCore installed, properly configured, and running
download hqly_player_worlds and drag and drop into your resources folder
add start hqly_player_worlds to your server.cfg file
edit config.lua
4.1. change permissionType to qbcore
4.2. change notificationFramework to qbcore
4.3. edit allowedRoles and put any job names you wish to be able to open the menu
to change either the permission or notification framework refer to the Permissions and Notification Framework Guides found below
ESX
make sure you have ESX installed and running
download hqly_player_worlds and drag and drop into your resources folder
add start hqly_player_worlds to your server.cfg file
edit config.lua
4.1. change permissionType to esx
4.2. change notificationFramework to esx
4.3. edit allowedRoles and put any job names you wish to be able to open the menu
to change either the permission or notification framework refer to the Permissions and Notification Framework Guides found below
Permissions Framework Guides
Ace Permissions
edit config.lua
1.1. change permissionType to ace
in your server.cfg add the appropriate ace permissions.
2.1. IE: add_ace group.police command.baitcar allow (make sure the command matches the command you have set in the config)
Discord Permissions
install & configure discordroles and hqly_perms: refer to Requirements section found above
edit config.lua
2.1. change permissionType to discord
place any desired Discord role IDs into allowedRoles
Command Permissions
edit config.lua
1.1. change permissionType to command
1.2. change commandPassword to your own password
authenticate in-game via /bc_onduty <password> (if you didnt change the default onDuty command)
QBCore Permissions
install & configure QBCore
edit config.lua
2.1. change permissionType to qbcore
2.2. edit allowedRoles to include any job roles names you wish to be able to open the menu
ESX Permissions
install & configure ESX
edit config.lua
2.1. change permissionType to qbcore
2.2. edit allowedRoles to include any job roles names you wish to be able to open the menu
No Permissions
edit config.lua
1.1. change permissionType to none
ADVANCED
Custom Permissions
edit config.lua
1.1. change permissionType to custom
find function canAccessMenu in client/auth.lua
2.1. find line: elseif config.permissionType == 'custom' then and add your verification call there, return true if can access menu
Notification Framework Guides
GTAV
edit config.lua
1.1. change notificationFramework to gtav
OkOkNotify
install & configure OkOkNotify
edit config.lua
2.1. change notificationFramework to okok
VCore-Noti
install & configure VCore-Noti
edit config.lua
2.1. change notificationFramework to vcore
T-Notify
install & configure T-Notify
edit config.lua
2.1. change notificationFramework to tnotify
B-Notify
install & configure B-Notify
edit config.lua
2.1. change notificationFramework to bnotify
Infinity Notify
install & configure Infinity Notify
edit config.lua
2.1. change notificationFramework to infinity
Atom-Notify
install & configure Atom-Notify
edit config.lua
2.1. change notificationFramework to atom
skeexsNotify
install & configure skeexsNotify
edit config.lua
2.1. change notificationFramework to skeexs
QBCore
install & configure QBCore
edit config.lua
2.1. change notificationFramework to qbcore
ESX
install & configure ESX
edit config.lua
2.1. change notificationFramework to esx
ADVANCED
Custom Notifications
edit config.lua
1.1. change notificationFramework to custom
find function doNotification in config.lua
2.1. find first instance of if config.notificationFramework == 'custom' then and add your success notification call under hat line using variable msg as the message text
2.2 find second instance of if config.notificationFramework == 'custom' then and add your error notification call under that line using variable msg as the message text
NOTE: if an option is left blank, that means that you can change it to anything!
Configuration
Explanation
Options
permissionType
Permission system to use to authenticate roles/jobs
discord, ace, none, qbcore, esx, command, custom
commandPassword
Will authenticate the player WITH the onduty command
allowedRoles
The job names or Discord role IDs that can open the menu
commands.staffTransferWorld
Command for staff to transfer their player to the desired Player World
commands.transferPlayerWorld
Command for staff to transfer a target player to a desired Player World
commands.staffAuthenticate
Command used to authenticate player with command-based permissions
commands.transferWorldRequest
Command used to send a teleport request to a target player
commands.transferWorldAccept
Command to accept a teleport request or invite
commands.transferWorldDeny
Command to deny a teleport request or invite
commands.transferWorld
Command to transfer the player to their own Player World
commands.transferWorldInvite
Command to invite a target player to a players Player World
commands.transferWorldKick
Command to kick a target player from own Player World
commands.getCurrentWorld
Command to notify player what Player World they are currently in
commands.mainWorld
Command to transfer back to the Main World
requestCoolDown
How often players can send world transfer requests in seconds. Leave at 0 for no cool down. Staff over-ride cooldown.
0 - 9999999
teleportCoolDown
How long in seconds a player will not be able to teleport for after a successful teleport between worlds. Leave at 0 for no cool down. Staff over-ride cooldown.
0 - 9999999
inviteResponseTime
How long in seconds an invite will stay active for before being removed
0 - 9999999
mainWorldTeleportCoolDown
Toggle whether the teleport cool down should apply when transferring to the Main World
Menu control alongside commands with added functionality
1.1. Ability to view which players are in your current player world
1.2. More player control of players in your world through menu options
Cooldown before teleport
World statuses: Open, Closed : with open players are able to see and join that player world without permission
Don’t hesitate to report any issues, offer any constructive criticism, or leave a suggestion!
If you have an idea you’d love to see come to life, don’t be afraid to get in touch!
Check out my other work:
[Bait-Car V2] | [X-Priorities] | [Play-Time] | [Ground]
I’ll post a preview soon, just been caught up with some stuff.
Yes, it is using the bucket routing, haven’t seen anything like this posted so I decided to go ahead and make it. Don’t see anything wrong with this release.
As for the scoreboard question, you would have to modify the scoreboard resource to correctly display the right number of whatever job.
Thank you for sharing your thoughts. While I understand your concerns, please be assured that I am diligently working towards resolving the issues and delivering a high-quality product in a timely manner. Unfortunately, I have encountered certain setbacks with the Zap hosting platform and real-life obligations, which have delayed the creation and posting of the preview. I appreciate your patience and understanding during this process.
I would like to clarify that making assumptions about the quality of my support based on a delay in the release of a preview is not representative of the level of support I offer. I take pride in providing my clients with comprehensive resources and continuously updating them. If you were to speak with any of my clients, you would know that I am committed to offering the best possible support. Thank you again for your understanding and support.
I am pleased to report that we have successfully restored our development server tonight, and we expect to upload the preview within the next few days.