Valence Teleporters
Valence HL2RP — Join Our Discord Created by the community behind Valence HL2RP. Join our Discord, visit the server where this mod began, and support the community behind its public release. Support Development on Ko-fi Appreciate the mod? Voluntary donations help fund continued development of this and other public mods. Donations provide no incentives, rewards, gameplay advantages, exclusive content, or early access… (more)
Valence HL2RP — Join Our Discord Created by the community behind Valence HL2RP. Join our Discord, visit the server where this mod began, and support the community behind its public release. Support Development on Ko-fi Appreciate the mod? Voluntary donations help fund continued development of this and other public mods. Donations provide no incentives, rewards, gameplay advantages, exclusive content, or early access to builds. Public releases remain free to everyone. Support is accepted in accordance with the DayZ EULA and Bohemia Interactive’s rules and does not purchase any benefit or authorize any breach of those rules. V_Teleporters Server-side teleporters and walk-in portals. Players either use a prompt on a configured object, or step into a portal. While they travel they are held in place on a black screen, then released with a clear view. Destinations are picked at random from the positions you list. Features []Object teleporters with your own action text, such as "Open Door" or "Deploy" []Black-screen transit with a configurable loading message []One destination, or a random pick from several []Optional sounds played at a position after a delay, with a shared cooldown per sound []Walk-in portals with a sprite, glow, and hum []Portal trip length and cooldown set per portal []Thrown items that pass through a portal are moved; items sitting still are left alone []Placeable dynamic portal: anyone who enters is sent to another dynamic portal Setup Add the mod on the server and the client. On first boot the server creates: $profile:VRP/V_Teleporters/V_Teleporters.json $profile:VRP/V_Teleporters/V_Portals.json Edit those files, then restart. Positions are x y z, in metres. An example of each file is in the mod under Example Config. Object teleporters { "TransitMessage": "Loading...", "Teleporters": [ { "Name": "Lab Door", "Position": "7310.47 47.57 6782.59", "Radius": 5, "ObjectClassName": "Land_Door_1", "ActionText": "Open Door", "SoundCooldownSeconds": 0, "TeleportPositions": [ "6289.87 8.65 7088.86" ], "Sounds": [] } ] } []TransitMessage is the text on the black screen. Leave it out and players see "Loading..." []Name is a unique label used in the server log []Position is the spot the object is matched against. Radius is how close it must be, in metres []ObjectClassName is the object's class, or the .p3d name for a map-baked object []ActionText is the prompt the player holds []TeleportPositions is where they arrive. Add more than one and one is chosen at random []Sounds is optional. Each entry is a SoundSet, a Position, and DelaySeconds counted from the teleport []SoundCooldownSeconds limits how often that sound set can play. 0 means no limit. Teleporters that share a sound set also share the timer The object trip lasts about 10 seconds. The player cannot move during it, and the screen clears when they can. Portals { "Portals": [ { "Name": "Lab Portal", "Position": "7305.0 47.5 6780.0", "Radius": 1.25, "SpriteHeight": 1.1, "TransitSeconds": 4.0, "CooldownSeconds": 5.0, "TeleportPositions": [ "6289.87 8.65 7088.86" ] } ] } []Position is the ground point. The sprite sits SpriteHeight metres above it (0 to 10) []Radius is the trigger size. Minimum 0.5 []TransitSeconds is how long the trip lasts (1 to 60) []CooldownSeconds is how long the portal sleeps after a use (0 to 300). 0 never sleeps TeleportPositions works the same way as on an object teleporter Walking or jumping in starts a trip. A player who lands in another portal is not sent straight back. After a cooldown they must step out and in again. To link
Not analyzed yet
modperf has not read this mod's scripts, so there is no report and it is left out of any stack it appears in. 1 live server in the crawl publishes it.
The worker downloads the mod from the Workshop and reads its Enforce Script — nothing is executed. Usually a few minutes. This page then shows the report.