Uses of Package
com.prineside.tdi2.utils
Packages that use com.prineside.tdi2.utils
Package
Description
Contains a fixed version of Input and Output from some of the older versions of Kryo, does not contain Kryo itself, meaning it is only good for a primitive data and is not a complete serialization solution.
Lua VM, only works in an interpreted mode, which allows it to support iOS.
The game itself.
Variants of
Ability
Abilities are what the player can use manually during the game (such things as a Fireball or Nuke).Variants of
Action
Actions are small records of player's activity he performs during the run, for example selling a tower or calling a wave.Variants of
BuffProcessor
Buff processors are single instances stored in BuffSystem, each of them is responsible for a single type of (de)buff.Components are simple containers for a set of fields, and they are used in a scenarios where these fields can be empty for an individual entities.
Variants of
Enemy
EnemySystem is responsible for handling the enemies and spawned enemies are stored in MapSystem.spawnedEnemiesA hard-coded lists of different types of everything, for example, types of enemies or towers.
-
Classes in com.prineside.tdi2.utils used by com.prineside.kryoClassDescriptionMethod marked as an overload (meaning there are multiple methods in the same class) which I can do nothing about because overload is forced by some super class / interface, or I've decided to keep like that because Java code makes more sense with that name.
-
Classes in com.prineside.tdi2.utils used by com.prineside.luaj
-
Classes in com.prineside.tdi2.utils used by com.prineside.luaj.debugClassDescriptionRegister for Serialization Kryo will register this class automatically at the start of the game
-
Classes in com.prineside.tdi2.utils used by com.prineside.luaj.libClassDescriptionRegister for Serialization Kryo will register this class automatically at the start of the game
-
Classes in com.prineside.tdi2.utils used by com.prineside.luaj.lib.jseClassDescriptionRegister for Serialization Kryo will register this class automatically at the start of the game
-
Classes in com.prineside.tdi2.utils used by com.prineside.tdi2ClassDescriptionNot Affects Game State Kryo serialization will skip fields and classes annotated with itUsage: FloatSorter sorter = FloatSorter.getInstance(); sorter.begin(); sorter.add("Foo", 5f); sorter.add("Bar", -3.5f); ...Method marked as an overload (meaning there are multiple methods in the same class) which I can do nothing about because overload is forced by some super class / interface, or I've decided to keep like that because Java code makes more sense with that name.Acts as a regular boolean field / flag which can be affected by multiple sources.Not Affects Game State Game will not compare annotated fields on sync checksSame as java.util.function Consumer (but it requires Android SDK 24+)Register for Serialization Kryo will register this class automatically at the start of the game
-
Classes in com.prineside.tdi2.utils used by com.prineside.tdi2.abilitiesClassDescriptionRegister for Serialization Kryo will register this class automatically at the start of the game
-
Classes in com.prineside.tdi2.utils used by com.prineside.tdi2.actionsClassDescriptionRegister for Serialization Kryo will register this class automatically at the start of the game
-
Classes in com.prineside.tdi2.utils used by com.prineside.tdi2.buffsClassDescriptionRegister for Serialization Kryo will register this class automatically at the start of the game
-
Classes in com.prineside.tdi2.utils used by com.prineside.tdi2.buffs.processorsClassDescriptionRegister for Serialization Kryo will register this class automatically at the start of the game
-
Classes in com.prineside.tdi2.utils used by com.prineside.tdi2.componentsClassDescriptionRegister for Serialization Kryo will register this class automatically at the start of the game
-
Classes in com.prineside.tdi2.utils used by com.prineside.tdi2.enemies
-
Classes in com.prineside.tdi2.utils used by com.prineside.tdi2.enemies.bosses
-
Classes in com.prineside.tdi2.utils used by com.prineside.tdi2.enumsClassDescriptionRegister for Serialization Kryo will register this class automatically at the start of the game
-
Classes in com.prineside.tdi2.utils used by com.prineside.tdi2.eventsClassDescriptionRegister for Serialization Kryo will register this class automatically at the start of the game
-
Classes in com.prineside.tdi2.utils used by com.prineside.tdi2.events.gameClassDescriptionRegister for Serialization Kryo will register this class automatically at the start of the game
-
Classes in com.prineside.tdi2.utils used by com.prineside.tdi2.explosionsClassDescriptionRegister for Serialization Kryo will register this class automatically at the start of the game
-
Classes in com.prineside.tdi2.utils used by com.prineside.tdi2.gameplayModsClassDescriptionRegister for Serialization Kryo will register this class automatically at the start of the game
-
Classes in com.prineside.tdi2.utils used by com.prineside.tdi2.gameplayMods.modsClassDescriptionRegister for Serialization Kryo will register this class automatically at the start of the game
-
Classes in com.prineside.tdi2.utils used by com.prineside.tdi2.gatesClassDescriptionRegister for Serialization Kryo will register this class automatically at the start of the game
-
Classes in com.prineside.tdi2.utils used by com.prineside.tdi2.ibxmClassDescriptionMethod marked as an overload (meaning there are multiple methods in the same class) which I can do nothing about because overload is forced by some super class / interface, or I've decided to keep like that because Java code makes more sense with that name.Register for Serialization Kryo will register this class automatically at the start of the game
-
Classes in com.prineside.tdi2.utils used by com.prineside.tdi2.itemsClassDescriptionRegister for Serialization Kryo will register this class automatically at the start of the game
-
Classes in com.prineside.tdi2.utils used by com.prineside.tdi2.managersClassDescriptionNot Affects Game State Game will not compare annotated fields on sync checksSame as java.util.function Consumer (but it requires Android SDK 24+)Register for Serialization Kryo will register this class automatically at the start of the game
-
Classes in com.prineside.tdi2.utils used by com.prineside.tdi2.managers.musicClassDescriptionRegister for Serialization Kryo will register this class automatically at the start of the game
-
Classes in com.prineside.tdi2.utils used by com.prineside.tdi2.managers.preferencesClassDescriptionSame as java.util.function Consumer (but it requires Android SDK 24+)
-
Classes in com.prineside.tdi2.utils used by com.prineside.tdi2.managers.preferences.categoriesClassDescriptionSame as java.util.function Consumer (but it requires Android SDK 24+)
-
Classes in com.prineside.tdi2.utils used by com.prineside.tdi2.managers.scriptClassDescriptionMethod marked as an overload (meaning there are multiple methods in the same class) which I can do nothing about because overload is forced by some super class / interface, or I've decided to keep like that because Java code makes more sense with that name.Register for Serialization Kryo will register this class automatically at the start of the game
-
Classes in com.prineside.tdi2.utils used by com.prineside.tdi2.managers.script.fsClassDescriptionRegister for Serialization Kryo will register this class automatically at the start of the game
-
Classes in com.prineside.tdi2.utils used by com.prineside.tdi2.minersClassDescriptionRegister for Serialization Kryo will register this class automatically at the start of the game
-
Classes in com.prineside.tdi2.utils used by com.prineside.tdi2.modifiersClassDescriptionRegister for Serialization Kryo will register this class automatically at the start of the game
-
Classes in com.prineside.tdi2.utils used by com.prineside.tdi2.modifiers.processorsClassDescriptionRegister for Serialization Kryo will register this class automatically at the start of the game
-
Classes in com.prineside.tdi2.utils used by com.prineside.tdi2.pathfinding
-
Classes in com.prineside.tdi2.utils used by com.prineside.tdi2.projectiles
-
Classes in com.prineside.tdi2.utils used by com.prineside.tdi2.screens
-
Classes in com.prineside.tdi2.utils used by com.prineside.tdi2.serializersClassDescriptionNot Affects Game State Kryo serialization will skip fields and classes annotated with it
-
Classes in com.prineside.tdi2.utils used by com.prineside.tdi2.shapesClassDescriptionMethod marked as an overload (meaning there are multiple methods in the same class) which I can do nothing about because overload is forced by some super class / interface, or I've decided to keep like that because Java code makes more sense with that name.
-
Classes in com.prineside.tdi2.utils used by com.prineside.tdi2.systemsClassDescriptionMethod marked as an overload (meaning there are multiple methods in the same class) which I can do nothing about because overload is forced by some super class / interface, or I've decided to keep like that because Java code makes more sense with that name.Not Affects Game State Game will not compare annotated fields on sync checksRegister for Serialization Kryo will register this class automatically at the start of the game
-
Classes in com.prineside.tdi2.utils used by com.prineside.tdi2.systems.randomEncounter
-
Classes in com.prineside.tdi2.utils used by com.prineside.tdi2.systems.randomEncounter.reward
-
Classes in com.prineside.tdi2.utils used by com.prineside.tdi2.systems.randomEncounter.typeClassDescriptionRegister for Serialization Kryo will register this class automatically at the start of the game
-
Classes in com.prineside.tdi2.utils used by com.prineside.tdi2.systems.randomEncounter.type.runningStarClassDescriptionRegister for Serialization Kryo will register this class automatically at the start of the game
-
Classes in com.prineside.tdi2.utils used by com.prineside.tdi2.systems.randomEncounter.type.starfall
-
Classes in com.prineside.tdi2.utils used by com.prineside.tdi2.tilesClassDescriptionNot Affects Game State Game will not compare annotated fields on sync checksRegister for Serialization Kryo will register this class automatically at the start of the game
-
Classes in com.prineside.tdi2.utils used by com.prineside.tdi2.towersClassDescriptionUsed on fields that accumulate frames and run some job once the field has reached some value (enough time passed).Not Affects Game State Game will not compare annotated fields on sync checksRegister for Serialization Kryo will register this class automatically at the start of the game
-
Classes in com.prineside.tdi2.utils used by com.prineside.tdi2.ui.actorsClassDescriptionMethod marked as an overload (meaning there are multiple methods in the same class) which I can do nothing about because overload is forced by some super class / interface, or I've decided to keep like that because Java code makes more sense with that name.Same as java.util.function Consumer (but it requires Android SDK 24+)
-
Classes in com.prineside.tdi2.utils used by com.prineside.tdi2.ui.componentsClassDescriptionMethod marked as an overload (meaning there are multiple methods in the same class) which I can do nothing about because overload is forced by some super class / interface, or I've decided to keep like that because Java code makes more sense with that name.
-
Classes in com.prineside.tdi2.utils used by com.prineside.tdi2.units
-
Classes in com.prineside.tdi2.utils used by com.prineside.tdi2.utilsClassDescriptionSimilar to BaseDrawable but has a smaller memory footprint and does not have a nameParameters represents set of parameters defining a particular CRC algorithm.Not Affects Game State Kryo serialization will skip fields and classes annotated with itMethod marked as an overload (meaning there are multiple methods in the same class) which I can do nothing about because overload is forced by some super class / interface, or I've decided to keep like that because Java code makes more sense with that name.Same as java.util.function Consumer (but it requires Android SDK 24+)Implementation of Batch which does not draw anything.Deprecated, use QuadDeprecated, use QuadRegister for Serialization Kryo will register this class automatically at the start of the gameThread-safe version of GDX's Pools Why thread safe: - Some events (like LogEntryAdd) may be triggered on a different threads - Multiple gameStates can be simulated on a different threads at the same timeMay also act like a Batch but will store vertex data into cache.
-
Classes in com.prineside.tdi2.utils used by com.prineside.tdi2.utils.loggingClassDescriptionRegister for Serialization Kryo will register this class automatically at the start of the game
-
Classes in com.prineside.tdi2.utils used by com.prineside.tdi2.utils.mapeditor
-
Classes in com.prineside.tdi2.utils used by com.prineside.tdi2.utils.simulation
-
Classes in com.prineside.tdi2.utils used by com.prineside.tdi2.utils.syncchecker.comparators
-
Classes in com.prineside.tdi2.utils used by com.prineside.tdi2.waves.processorsClassDescriptionRegister for Serialization Kryo will register this class automatically at the start of the game