> For the complete documentation index, see [llms.txt](https://duckys-playground.gitbook.io/wave/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://duckys-playground.gitbook.io/wave/functions/signal.md).

# Signal

### Can Signal Replicate

{% code lineNumbers="true" %}

```typescript
<bool> cansignalreplicate(<RBXScriptSignal signal>)
```

{% endcode %}

* Checks if `RBXScriptSignal` is capable of being replicated (i.e., fired to the server or across the client-server boundary).

***

### Disable Connection

{% code lineNumbers="true" %}

```typescript
<void> disableconnection(<RBXScriptConnection> Connection)
```

{% endcode %}

* Disables `Connection`.

***

### Enable Connection

{% code lineNumbers="true" %}

```typescript
<void> enableconnection(<RBXScriptConnection> Connection)
```

{% endcode %}

* Enables `Connection`.

***

### Fire Signal

{% code lineNumbers="true" %}

```typescript
<void> firesignal(<RBXScriptSignal> Signal, <variant?> Args...)
```

{% endcode %}

* Fires all signals connected to the `signal`. If given, the arguments will be used to call the function.

***

### Get All Replicate Signals

{% code lineNumbers="true" %}

```typescript
<table> getallreplicatesignals(<void>)
```

{% endcode %}

* Returns a table containing all `RBXScriptSignal` objects in the game that are capable of replication.

***

### Get Connections

{% code lineNumbers="true" %}

```typescript
<table> getconnections(<RBXScriptSignal> Signal)
```

{% endcode %}

* Returns a `table` with all connections to the given `signal`.

#### Connections:

| Connection |                Description                |
| :--------: | :---------------------------------------: |
|  .Function | The function connected to the connection. |
|   :Enable  |          Enables the connection.          |
|  :Disable  |          Disables the connection.         |
|    :Fire   |           Fires the connection.           |

***

### Get Signal Arguments

{% code lineNumbers="true" %}

```typescript
<table> getsignalarguments(<RBXScriptConnection conn>)
```

{% endcode %}

* Retrieves the arguments passed to a specific `RBXScriptConnection` when it was last fired.

***

### Hook Signal

{% code lineNumbers="true" %}

```typescript
<void> hooksignal(<RBXScriptSignal> Signal, <function> callback)
```

{% endcode %}

* Intercepts signal invocations. When the `Signal` is fired, the `callback` is called for each Lua connection with an info table and arguments. Returning <mark style="color:green;">`true`</mark> from the callback triggers the original connection.&#x20;

> Note: `hooksignal` cannot intercept C connections or CoreScript Lua connections.

***

### Is Connection Enabled

{% code lineNumbers="true" %}

```typescript
<bool> isconnectionenabled(<RBXScriptConnection> Connection)
```

{% endcode %}

* Returns <mark style="color:green;">`true`</mark> if a connection is enabled.

***

### Is Signal Hooked

<pre class="language-typescript" data-line-numbers><code class="lang-typescript"><strong>&#x3C;void> issignalhooked(&#x3C;RBXScriptSignal> Signal)
</strong></code></pre>

* Returns <mark style="color:green;">`true`</mark> if `Signal` is hooked.

***

### Replicate Signal

{% code lineNumbers="true" %}

```typescript
<void> replicatesignal(<RBXScriptSignal signal>, <var ...args>)
```

{% endcode %}

* Fires a `RBXScriptSignal` locally, simulating its activation with the provided arguments.

***

### Unhook Signal

<pre class="language-typescript" data-line-numbers><code class="lang-typescript"><strong>&#x3C;void> unhooksignal(&#x3C;RBXScriptSignal> Signal)
</strong></code></pre>

* Unhooks a signal hooked with `hooksignal`.

***


---

# 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://duckys-playground.gitbook.io/wave/functions/signal.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.