This tool lets you design your Pager Network for Inferno Collection's Pager Reborn FiveM resource.
There are three kinds of nodes:
A folder is for organization only; it cannot be paged. For example, if Fire and EMS circuits are separate on your server, you might put them in separate folders. This allows for separate address as well, for example: fire.station1 & ems.station1.
A group is similar to a folder in that it is used for organizing capcodes, however unlike a folder, it can be paged. An example of group usage, is for whole fire stations: Fire Station One could be the parent group, then each appliance could be a capcode. This way, so long as the group is applied to each required player, you could page the group if you wanted a whole-station response, versus the individual appliances.
Expanding on the prior example, having one group per station would allow you to use wildcard permissions (e.g. fire.stationone.*), which would then allow players to select their appliance as needed.
A capcode is the smallest kind of node, and cannot have children; it should represent a single "thing", whether that be an appliance, a role/person, or a small number of people.
Permissions are generated automatically from node names and IDs unless overridden.
Invalid nodes are highlighted and will block export.
There are two kinds of permission:
Roles are designed to suit large groups of players. For example "Firefighter" or "Paramedic" might be a role, which could grant access to all Fire/EMS Stations. There can also be more specific roles, for example "HAZMAT" or "USAR", which could grant access to specialist capcodes. Players are assigned roles by listing their identifier(s) within the roles themselves - the name field is only for your reference and does not need to match a player's username.
Players behave the same as roles, but are specific only to one player, and act as an override. For example, if a player has the "Firefighter" role, and that role disallows them from accessing "my.cap.code", but they also have an individual player permission entry that allows them access, then the player permissions overrides the role.
For both Roles and Player entries, there are four options:
Nodes listed here will be "forced upon" players, in that they will automatically be joined when entering the server without any input from the players. This could be used for an "All Players" capcode for example. If a node listed in Default is not also listed in Allowed, then players will not be able to remove themselves from the node.
Nodes listed here can be joined and left by players freely. For example, "Firefighters" might be Allowed to join all Fire Stations, enabling them to join the required node for the Station they are manning for that play session.
Nodes listed here cannot be joined or left by players freely. This option is useful if, for example, you Allow a player access to a group containing multiple capcodes via a wildcard (e.g., "fire.stations.*"), but then want to prevent a specific station being accessible (e.g., "fire.station.hq"). Generally, you'll want to design your network such that you do not need to use Disallow, and "private" or "special" nodes are separate entirely.
Nodes listed here can be paged by players. Only players who handle paging need this permission. For example, if you have players who are Firefighters, and players who are Dispatchers: Firefighters would need their Stations/Trucks/Etc. added to their Allowed list, but wouldn't need anything in their Pageable, while the reverse would be true for Dispatchers, with nothing in their Allowed, but all Stations/Trucks/Etc. in their Pageable.
Permissions support wildcards, which allows easier assigning of large collections of nodes. Wildcards can be used in the Designer by holding the Shift key while selecting a Folder or Group. For example, if you have Fire Stations set up something like this: "fire.station.one", "fire.station.two", etc., where "fire.station" is a group or folder, you can assign "fire.station.*" to give access to all child nodes.
Roles support an optional "Ace Permission" input. When the server loads, this will automatically assign the Pager Role to any players with the matching Ace Permission. For example, you might have the principal group.fire_chiefs. You could then create an ace called all_fire_calls and assign it to that group (add_ace group.fire_chiefs "all_fire_calls" allow). In the Ace Permission field, you would enter all_fire_calls and assign all Fire capcodes to that role. As a result, any player in group.fire_chiefs will automatically receive all Fire capcodes.