# Potion Data

This section is used for selecting the potion type, model data, and original potion effects.

### Original Effects

This is a weird option. Let me give you an example. If you select STRENGTH as potion type, and enabled the option, when executing commands, it will also give you the <mark style="color:blue;">strength effect without</mark> using extra command. I don't see any usage for here, so I will probably deprecate it in major versions.

Potion Type List: [https://hub.spigotmc.org/javadocs/spigot/org/bukkit/potion/PotionType.html](https://hub.spigotmc.org/javadocs/spigot/org/bukkit/potion/PotionType.html)

{% hint style="danger" %}
Original Effects is OVERLY complicated and plugin already covers it with command, so will be removed one or two version after 4.0 STABLE update. Please use regular /effect command if you want to give the original potion effect. Come on, one single extra command.

Unlike command overhaul, /aetherpotions migrate <mark style="color:red;">**will not**</mark> cover this change.
{% endhint %}

## Configuration Table

<table data-full-width="true"><thead><tr><th width="193">Variable</th><th width="400">Description</th><th>Example/Expected Value</th></tr></thead><tbody><tr><td>customModelData</td><td>Custom model data. You can use this for custom textures.</td><td>Integer</td></tr><tr><td>potionType</td><td>Potion type. Things like Speed, Strength etc... <mark style="color:red;">Do not</mark> put prefixes like STRONG, LONG etc. Just put the plain old potion type and configure level/time below.</td><td>STRENGTH</td></tr><tr><td>originalEffect [Optional]</td><td>This option is needed if you need to apply original potion effect.</td><td>true/false</td></tr><tr><td>extended (Requires originalEffect)</td><td>If you want to extend the potion time same as brewing, you can use this option.</td><td>true/false</td></tr><tr><td>upgraded (Requires originalEffect)</td><td>If you want to upgrade the potion same as brewing (Level 2), you can use this option.</td><td>true/false</td></tr></tbody></table>

With this configuration, our updated file:

```yaml
flight:
  displayName: '&6Flight Potion'
  lore:
    - '&9Food & Drinks'
    - '&9Flight I (04:00)'
  isSplash: false
  deleteBottle: false
  instantDrink: false
  cooldown: 480
  data:
    potionType: LUCK
```
