buildpieces:personal_portals
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
buildpieces:personal_portals [2024/12/01 20:49] – paddle | buildpieces:personal_portals [2025/08/13 06:49] (current) – arapeta | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== Portals🌀 ====== | + | ====== |
- | Portals | + | **Personal |
- | These portals have acessable interface when clicking on it where you can choose the destination you are gonna travel to, this means that you dont need a portal | + | |
+ | With Personal Portals, players can target specific destinations directly, eliminating the need to construct a separate home portal for each remote location, and can completely replace the original teleporters. | ||
- | + | ---- | |
+ | ===== Overview ===== | ||
+ | Personal and Public Portals serve as critical tools for navigating the game world efficiently: | ||
+ | |||
+ | * **Personal Portals**: Constructed by players using standard portal materials, these are linked to the builder’s Steam ID and provide a personalized teleportation network. Players no longer need to construct a separate home portal for every remote portal, as each Personal Portal can independently target a specific destination. | ||
+ | * **Public Portals**: Admin-exclusive constructs that offer shared teleportation capabilities accessible to all players. | ||
+ | |||
+ | Each type of portal has unique features tailored for specific purposes, enhancing navigation and resource management. | ||
+ | |||
+ | ---- | ||
+ | |||
+ | ===== Personal Portals ===== | ||
+ | {{ : | ||
+ | Personal Portals are player-built teleportation devices offering flexibility and control within a private network. | ||
+ | |||
+ | ==== Construction and Features ==== | ||
+ | * **Materials**: | ||
+ | * **Naming**: Names are assigned by the builder and linked account-wide via Steam ID. To rename, hold **Left Shift** while interacting with the portal. | ||
+ | * **Target Storage**: The destination is stored physically on the portal itself. | ||
+ | * **One-way connection**: | ||
+ | |||
+ | ==== Connectivity ==== | ||
+ | * **Connections**: | ||
+ | * Can link to any other Personal Portal owned by the same Steam ID. | ||
+ | * Can connect to any Public Portals. | ||
+ | * **Access**: | ||
+ | * Other players **can** use your Personal Portals to reach set destinations. If they can get to your portal, they can use it. | ||
+ | * In warded areas, players with Ward permissions can modify portal names and destinations. | ||
+ | |||
+ | ==== Cautions ==== | ||
+ | * **Ward Access** grants the guest with access to your entire portal network from any of your portals in the Ward. Be careful who you allow. | ||
+ | * Entering another player’s Personal Portal without destination knowledge may lead to: | ||
+ | * **Remote locations** with no return portal. | ||
+ | * **Warded areas** where you could be trapped. (Requests to a Thane to release you WILL be noted!) | ||
+ | * **Highly hazardous** locations with no easy escape. | ||
+ | * **Best Practice**: Only use another player’s portal if you are certain of its destination. | ||
+ | * Portals __not__ in a Ward can only be changed by the Portal owner | ||
+ | * Good manners would dictate asking before you use a random person' | ||
+ | |||
+ | ---- | ||
+ | |||
+ | ===== Public Portals ===== | ||
+ | {{ : | ||
+ | Public Portals, managed by admins, provide shared teleportation options for the entire player base. | ||
+ | |||
+ | ==== Construction and Features ==== | ||
+ | * **Builder**: | ||
+ | * **Naming**: Assigned by admins and unchangeable by players. | ||
+ | |||
+ | ==== Connectivity and Targeting ==== | ||
+ | * **Targeting Options**: | ||
+ | * Can link to any other Public Portal. | ||
+ | * Can connect to a Personal Portal tied to players Steam ID. | ||
+ | * **Dynamic Targeting**: | ||
+ | * Targets are set locally by the player using the portal, not stored on the portal itself. | ||
+ | * This allows players to dynamically choose destinations while using Public Portals. | ||
+ | * **Automatic Targeting**: | ||
+ | * After teleporting to a Public Portal, the portal automatically sets its target to the previously used portal, enabling quick returns. | ||
+ | * **Note**: | ||
+ | * Public Portals can only be used by players that have built at least one Personal Portal. | ||
+ | |||
+ | ---- | ||
+ | |||
+ | ===== Best Practices for Teams ===== | ||
+ | |||
+ | Efficient use of Personal and Public Portals can significantly enhance teamwork and exploration: | ||
+ | |||
+ | ==== Personal Portal Management ==== | ||
+ | * **Each team member** should construct and maintain **one Personal Portal**. | ||
+ | * Assign one player as the **" | ||
+ | |||
+ | ==== Team Strategies ==== | ||
+ | * **Using the Portal Master’s Network**: | ||
+ | * Team members can connect to remote locations through the portal master’s Personal Portals. | ||
+ | * **Remote Portal Setup**: | ||
+ | * Set remote portals to target the home base. | ||
+ | * Warded remote portals can be modified by teammates with permissions. | ||
+ | * **Exploration Setup**: | ||
+ | * Place temporary Personal Portals when exploring new areas. | ||
+ | * The portal master can later rebuild and integrate these into the main network using their Steam ID. | ||
+ | |||
+ | {{: | ||
+ | ---- | ||
+ | |||
+ | ===== Conclusion ===== | ||
+ | |||
+ | By mastering the mechanics of Personal and Public Portals, players can create an efficient teleportation network. Teams can further enhance their connectivity by designating a portal master to oversee the system, ensuring seamless exploration and resource management. | ||
buildpieces/personal_portals.1733086190.txt.gz · Last modified: 2024/12/01 20:49 by paddle