This page is not available in the language you have chosen. It will be displayed in English by default. If you would like to view it in a different language, you can try selecting another language.
Forces the carryable to be carried by the provided player, teleporting it into their hands.
If not in a viable state to carry the item (such as in a vehicle), or if the player fails the device's filters, it is ignored.
Verse using statement |
using { /Fortnite.com/Devices } |
ForcePlayerToCarry<public>(Player:player)<transacts><no_rollback>:void
Parameters
ForcePlayerToCarry takes the following parameters:
| Name | Type | Description |
|---|---|---|
Player |
player |
Attributes, Specifiers, and Effects
Specifiers
The following specifiers determine how you can interact with ForcePlayerToCarry in your programs. For the complete list of specifiers, see the Specifiers Page.
| Specifier | Meaning |
|---|---|
public |
The identifier is universally accessible. You can use this on modules, classes, interfaces, structs, enums, methods, and data. |
Effects
The following effects determine how ForcePlayerToCarry behaves in your programs. For the complete list of effects, see the Effect Specifers section of the Specifiers Page.
| Effect | Meaning |
|---|---|
transacts |
This effect indicates that any actions performed by the function can be rolled back. The transacts effect is required any time a mutable variable (var) is written. You'll be notified when you compile your code if the transacts effect was added to a function that can't be rolled back. Note that this check is not done for functions with the native specifier. |
no_rollback |
This is the default effect when no exclusive effect is specified. The no_rollback effect indicates that any actions performed by the function cannot be undone and so the function cannot be used in a failure context. This effect cannot be manually specified. |