Variables are used internally to create both advanced actions and conditions at the same time- and that much quicker! A lot of the following variables can thus be used as conditions and, in many cases, as actions as well.
Not only that - they can also be used in so-called expressions. So you can even do calculations with these variables!

## Default variables

### ❓ ActiveQuests



### ❓ Advancement



### ❓ Block



### ❓ Chance



### ❓ Climbing



### ❓ CompletedObjectiveIDsOfQuest



### ❓ CompletedQuests



### ❓ Condition



### ❓ ContainerInventory



### ❓ CurrentBiome



### ❓ CurrentPositionX



### ❓ CurrentPositionY



### ❓ CurrentPositionZ



### ❓ CurrentWorld



### ❓ DayOfWeek



### ❓ DistanceToLocation



### ❓ EnderChest



### ❓ Experience



### ❓ ExperienceLevel



### ❓ False



### ❓ Flying



### ❓ FlySpeed



### ❓ FoodLevel



### ❓ GameMode



### ❓ Glowing



### ❓ Health



### ❓ InLava



### ❓ InWater



### ❓ Inventory



### ❓ ItemInInventoryEnchantments



### ❓ MaxHealth



### ❓ Money



### ❓ Name



### ❓ NearbyEntityCount



### ❓ Op



### ❓ Permission



### ❓ Ping



### ❓ PlaytimeTicks



### ❓ PlaytimeMinutes



### ❓ PlaytimeHours



### ❓ QuestAbleToAccept



### ❓ QuestOnCooldown



### ❓ QuestPoints



### ❓ QuestReachedMaxAccepts



### ❓ QuestReachedMaxCompletions



### ❓ QuestReachedMaxFails



### ❓ RandomNumberBetweenRange



### ❓ ReflectionStaticBoolean



### ❓ ReflectionStaticDouble



### ❓ ReflectionStaticFloat



### ❓ ReflectionStaticInteger



### ❓ ReflectionStaticString



### ❓ Sleeping



### ❓ Saturation



### ❓ Sneaking



### ❓ Sprinting



### ❓ Swimming



### ❓ True



### ❓ WalkSpeed



### ❓ Weather



### ❓ Statistic



## Tag Variables

NotQuests has a powerful **tag system**: store a custom value on a player — a reputation score, a faction name, a `hasMetTheKing` flag — and then read or change it anywhere variables work (conditions, actions, objectives, even inside expressions).

First create a tag with `/qa tags create <Type> <name>` (types: `Integer`, `Double`, `Float`, `Boolean`, `String`). Then use the matching variable below. In commands the tag name is **positional** (`TagInteger reputation add 10`); inside an expression use the `TagInteger(TagName:reputation)` form instead.

For a full, practical walkthrough, see the [reputation system tutorial](/docs/tutorials/creating-a-reputation-system-with-tags).

### ❓ TagInteger



### ❓ TagDouble



### ❓ TagFloat



### ❓ TagBoolean



### ❓ TagString



## [PlaceholderAPI](https://github.com/PlaceholderAPI/PlaceholderAPI/releases) Integration Variables

### ❓ PlaceholderAPINumber



### ❓ PlaceholderAPIString



## [Towny](https://github.com/TownyAdvanced/Towny/releases) Integration Variables

### ❓ TownyNationName



### ❓ TownyNationTownCount



### ❓ TownyTownPlotCount



### ❓ TownyTownResidentCount



## [Floodgate](https://github.com/GeyserMC/Floodgate) Integration Variables

### ❓ FloodgateIsFloodgatePlayer



## BetonQuest 3 Integration Variables

These variables are only available when BetonQuest 3.0.0 or newer is installed. BetonQuest 1.x and 2.x are not supported.

### ❓ BetonQuestCondition