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.
If the mod box is spawned, respawn it as the next valid entry in the list without triggering BoxDestroyEvent.
- If the mod box is not spawned, that will be the next mod box.
- The list wraps, which means the first index is considered directly after the last index.
- Does nothing if this device is disabled or Possible Mods is not set to
Custom List.
Verse using statement |
using { /Fortnite.com/Devices } |
CycleToNextValidIndex<public>()<transacts><no_rollback>:void
Parameters
CycleToNextValidIndex does not take any parameters.
Attributes, Specifiers, and Effects
Specifiers
The following specifiers determine how you can interact with CycleToNextValidIndex 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 CycleToNextValidIndex 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. |