public abstract class AbstractSpongeDataProcessor<M extends org.spongepowered.api.data.manipulator.DataManipulator<M,I>,I extends org.spongepowered.api.data.manipulator.ImmutableDataManipulator<I,M>> extends Object implements DataProcessor<M,I>
Constructor and Description |
---|
AbstractSpongeDataProcessor() |
Modifier and Type | Method and Description |
---|---|
int |
getPriority()
Gets the priority of this processor.
|
boolean |
supports(org.spongepowered.api.entity.EntityType entityType) |
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait
createFrom, fill, fill, from, remove, set, supports, with
public int getPriority()
DataProcessor
Key
can have
multiple DataProcessor
s such that mods introducing
changes to the game can provide their own DataProcessor
s
for specific cases. The notion is that the higher the priority, the
earlier the processor is used. If for any reason a processor's method
is returning an Optional.empty()
or
DataTransactionResult
with a failure, the next processor in
line will be used. By default, all Sponge processors are with a
priority of 100.getPriority
in interface DataProcessor<M extends org.spongepowered.api.data.manipulator.DataManipulator<M,I>,I extends org.spongepowered.api.data.manipulator.ImmutableDataManipulator<I,M>>