Package ch.njol.skript.lang
package ch.njol.skript.lang
Contains all code related to parsing scripts.
-
ClassDescriptionA condition which must be fulfilled for the trigger to continue.Represents an element that can print details involving an event.Represents an expression that can be used as the default value of a certain type or event.An effect which is unconditionally executed when reached, and execution will usually continue with the next item of the trigger after this effect is executed (the stop effect for example stops the trigger, i.e.A
Section
that may also be used as an effect, meaning there may be no section to parse.Represents the Effect aspect of an EffectSection.Expression<T>Represents an expression.Represents an expression's information, for use when creating new instances of expressions.A list of expressions.Used to define in which order to parse expressions.An InputSource represents a syntax that can provide a value forExprInput
to use.Literal<T>A literal, e.g.LiteralList<T>A list of literals.Represents a loop section.Used to provide context as to where an element is being parsed from.A section that can decide what it does with its contents, as code isn't parsed by default.ASection
implementing this interface can execute a task when it is exited by an'exit'
or'return'
effect.To be used in sections that delay the execution of their code through aTrigger
.Deprecated.A SkriptEvent is like a condition.The listening behavior of a Skript event.SkriptEventInfo<E extends SkriptEvent>Used for parsing my custom patterns.
Note: All parse methods print one error at most xor any amount of warnings and lower level log messages.Supertype of conditions and effectsRepresents a general part of the syntax.SyntaxElementInfo<E extends SyntaxElement>Represents a trigger item, i.e.Represents a section of a trigger, e.g.A literal which has yet to be parsed.Variable<T>Represents a string that may contain expressions, and is thus "variable".This interface provides methods forCondition
s to provide expected and received values forEffAssert
or others to use to in debugging or testing scenarios.
Structure
methods should be used.