> For the complete documentation index, see [llms.txt](https://documentation.jaksam-scripts.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.jaksam-scripts.com/drugs-creator/client/manually-start-drugs-effects.md).

# Manually start drugs effects

Trigger to start drug effects (you may prefer to trigger this from server side)

## Event

```lua
TriggerEvent("drugs_creator:drugEffects", takingMethod, effects, effectsDuration, cumulativeEffects)
```

### Parameters

| Name                | Data Type | Description                                                                                            |
| ------------------- | --------- | ------------------------------------------------------------------------------------------------------ |
| `takingMethod`      | string    | How the player will take the drug                                                                      |
| `effects`           | table     | An array of strings containing all effects you want to add                                             |
| `effectsDuration`   | integer   | Seconds the effects will last                                                                          |
| `cumulativeEffects` | table     | OPTIONAL - Array containing the cumulative effects you want to add (check the examples for the format) |

### Taking methods

* `"pill"`
* `"drink"`
* `"smoke"`
* `"needle"`

### Effects

* `"visual_shaking"`
* `"drunk_walk"`
* `"fall"`
* `"pink_visual"`
* `"green_visual"`
* `"confused_visual"`
* `"yellow_visual"`
* `"blurred_visual"`
* `"red_visual"`
* `"foggy_visual"`
* `"blue_visual"`
* `"armor50"`
* `"armor100"`
* `"health50"`
* `"health100"`
* `"sprint_faster"`
* `"swim_faster"`
* `"infinite_stamina"`
* `"remove_old_effects"`
* `"vehicle_stalker"`
* `"ghost"`

### Cumulative effects `actions`

* `increaseArmor`
* `decreaseArmor`
* `increaseHealth`
* `decreaseHealth`
* `increaseHunger`
* `decreaseHunger`
* `increaseThirst`
* `decreaseThirst`
* `increaseStress`
* `decreaseStress`

## Example - Client side

```lua
RegisterCommand("effects", function() 
    local takingMethod = "pill"
    local effects = {
        "drunk_walk",
        "swim_faster",
        "green_visual",
    }

    local cumulativeEffects = {
        {action = "increaseArmor", value = 50},
        {action = "decreaseThirst", value = 15},
    }

    local effectsDuration = 120 -- seconds

    TriggerEvent("drugs_creator:drugEffects", takingMethod, effects, effectsDuration, cumulativeEffects)
end)
```

## Example - Server side

```lua
RegisterCommand("effects", function(playerId) 
    local takingMethod = "pill"
    local effects = {
        "drunk_walk",
        "swim_faster",
        "green_visual",
    }

    local cumulativeEffects = {
        {action = "increaseArmor", value = 50},
        {action = "decreaseThirst", value = 15},
    }

    local effectsDuration = 120 -- seconds

    TriggerClientEvent("drugs_creator:drugEffects", playerId, takingMethod, effects, effectsDuration, cumulativeEffects)
end)
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://documentation.jaksam-scripts.com/drugs-creator/client/manually-start-drugs-effects.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.