# Other Errors

## Multiple players

Sometimes, an event can involve more than one player. In that case, the `player` expression becomes quite ambiguous, so you'll need to use a different expression. Some effects will also default to the `event-player` if not specified, which could cause issues if you meant to perform that action on another.

### Attacker, victim, and shooter

The `attacker` and `victim` expressions are event-values specific to the `on damage:` and `on death:` events. These will replace the `player` expression in your code.

{% hint style="info" %}
Why? Because the `on damage:` and `on death:` events could involve multiple players. Consider the following scenario: player A whacks player B with an iron sword. If you were to use `player`, who would that refer to? Player A (the `attacker`)? Or player B (the `victim`)? Skript won't know which player you mean, so you'll have to be a little more specific.
{% endhint %}

The `shooter` expression is exactly the same; replacing `attacker` in events like `on projectile hit:` and replacing `player` in events such as `on shoot:`.

### Recipients

The send effect has the syntax `send %string(s)% [to %player(s)%]`, and will default to the `event-player` if you do not specify a recipient. Some tutorials or examples omit the `to player` at the end because they want to send to the `player`, which Skript does by default. And in such cases this works as intended.

However, not being taught the full syntax may (incorrectly) imprint onto viewers the idea that Skript magically sends the message to its intended target. This causes some to not know that you can (and sometimes must) specify receiver(s).

What happens if you don't want to send the message to the `player`? What if you wanted to send it to a variable or a command argument? You'll need to add `to %someone%` at the end of the line.


---

# Agent Instructions: 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:

```
GET https://x8ight.gitbook.io/syntask/issues/errors/other-errors.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.