TicketTypes (SpongeAPI 8.0.0 API)

java.lang.Object
- org.spongepowered.api.world.server.TicketTypes

```
public final class TicketTypes
extends Object
```
Types of tickets that can be requested via the ChunkManager.

Field Summary

Fields
Modifier and Type	Field	Description
`static DefaultedRegistryReference<TicketType<Vector3i>>`	`PORTAL`	Represents `tickets` that are intended to ensure that the target `chunks` around a `Portal` are loaded, ready to accept `entities` that travel through it.
`static DefaultedRegistryReference<TicketType<Entity>>`	`POST_TELEPORT`	Represents `tickets` that are intended to ensure that the target `chunks` around an `Entity` are loaded after teleportation.
`static DefaultedRegistryReference<TicketType<Vector3i>>`	`STANDARD`	Represents `tickets` that ensures the target `chunks` are loaded, but are not guaranteed to be loaded at any time in the future, that is, the lifetime of such a ticket is effectively one `tick`.

Method Summary

All Methods Static Methods Concrete Methods
Modifier and Type Method Description

static Registry<TicketType<?>> registry()
- Methods inherited from class java.lang.Object
  clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

- Field Detail
  - STANDARD
```
public static final DefaultedRegistryReference<TicketType<Vector3i>> STANDARD
```
    Represents tickets that ensures the target chunks are loaded, but are not guaranteed to be loaded at any time in the future, that is, the lifetime of such a ticket is effectively one tick.
    The position represented by the Vector3i is a chunk position, not a block position, so when requesting a ticket using ChunkManager.requestTicket( TicketType, Vector3i, Object, int), the second and third parameter should be the same.
  - PORTAL
```
public static final DefaultedRegistryReference<TicketType<Vector3i>> PORTAL
```
    Represents tickets that are intended to ensure that the target chunks around a Portal are loaded, ready to accept entities that travel through it.
    The position represented by the Vector3i is a block position, specifically, it is intended it is that of the exit point of a portal. When requesting a ticket using ChunkManager.requestTicket( TicketType, Vector3i, Object, int), the second parameter represents a chunk position, the third parameter represents a block position.
  - POST_TELEPORT
```
public static final DefaultedRegistryReference<TicketType<Entity>> POST_TELEPORT
```
    Represents tickets that are intended to ensure that the target chunks around an Entity are loaded after teleportation.
- Method Detail
  - registry
```
public static Registry<TicketType<?>> registry()
```