1
0
Fork
You've already forked invisibility
1

Please separate the invisible player table from the function namespace #4

Closed
opened 2024年11月14日 03:39:19 +01:00 by Bastrabun · 1 comment

If a player enters who is called "invisible", he might overwrite the invisible function. Or if someone enters with name "effect_time"

That's because if a player goes invisible, the data structure looks like this:

invisbility = {
 myplayername = true,
 invisible = <function>,
 effect_time = 180
}
If a player enters who is called "invisible", he might overwrite the invisible function. Or if someone enters with name "effect_time" That's because if a player goes invisible, the data structure looks like this: ``` invisbility = { myplayername = true, invisible = <function>, effect_time = 180 } ```

Fixed, thanks for the heads up :)

Fixed, thanks for the heads up :)
Sign in to join this conversation.
No Branch/Tag specified
master
No results found.
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
tenplus1/invisibility#4
Reference in a new issue
tenplus1/invisibility
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?