Skip to content

Add cooldowns tutorial page#13

Open
ahmadmsaleem wants to merge 9 commits intoSkriptLang:masterfrom
ahmadmsaleem:feature/eult-suggestions
Open

Add cooldowns tutorial page#13
ahmadmsaleem wants to merge 9 commits intoSkriptLang:masterfrom
ahmadmsaleem:feature/eult-suggestions

Conversation

@ahmadmsaleem
Copy link
Copy Markdown

Summary

  • Adds a new "Cooldowns" tutorial page to the scripting section
  • Covers command cooldowns, item cooldowns, variable-based cooldowns, and delay-based warmups
  • Includes practical examples, tips, and a comparison summary table
  • Adds the page to the scripting index

Sources used as an inspo:

Copy link
Copy Markdown
Member

@Efnilite Efnilite left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

looks pretty good in general

Comment thread src/content/docs/scripting/cooldowns.md Outdated
Comment thread src/content/docs/scripting/cooldowns.md Outdated
Comment thread src/content/docs/scripting/cooldowns.md Outdated
Comment thread src/content/docs/scripting/cooldowns.md Outdated
Comment thread src/content/docs/scripting/cooldowns.md Outdated
Comment thread src/content/docs/scripting/cooldowns.md Outdated
Copy link
Copy Markdown
Member

@sovdeeth sovdeeth left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think command cooldowns fit here. They should be covered in a command tutorial.

@ahmadmsaleem
Copy link
Copy Markdown
Author

I will close it

@sovdeeth
Copy link
Copy Markdown
Member

why did you close it? I just mentioned command cooldowns, not all the rest

@ahmadmsaleem ahmadmsaleem reopened this Apr 20, 2026
ahmadmsaleem and others added 8 commits April 20, 2026 21:02
Co-authored-by: Efnilite <35348263+Efnilite@users.noreply.github.com>
Co-authored-by: Efnilite <35348263+Efnilite@users.noreply.github.com>
Co-authored-by: Efnilite <35348263+Efnilite@users.noreply.github.com>
Co-authored-by: Efnilite <35348263+Efnilite@users.noreply.github.com>
Co-authored-by: Efnilite <35348263+Efnilite@users.noreply.github.com>
Co-authored-by: Efnilite <35348263+Efnilite@users.noreply.github.com>
@ahmadmsaleem
Copy link
Copy Markdown
Author

I removed the command cooldown!


If you're using variable-based cooldowns (the `{cooldown::...}` pattern), keep in mind that these are global variables. They get saved to disk and persist through restarts, which is great for long cooldowns like daily rewards but unnecessary for short ones like a 5-second ability cooldown. For short cooldowns that don't need to survive restarts, consider using temporary global variables: `{-cooldown::...}`.

For short cooldowns that don't need to survive restarts, consider using a storage solution that keeps data in memory only, so you're not writing to disk every few seconds for cooldowns that will expire before anyone notices. No newline at end of file
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
For short cooldowns that don't need to survive restarts, consider using a storage solution that keeps data in memory only, so you're not writing to disk every few seconds for cooldowns that will expire before anyone notices.

incorrect info


## A Note on Variables

If you're using variable-based cooldowns (the `{cooldown::...}` pattern), keep in mind that these are global variables. They get saved to disk and persist through restarts, which is great for long cooldowns like daily rewards but unnecessary for short ones like a 5-second ability cooldown. For short cooldowns that don't need to survive restarts, consider using temporary global variables: `{-cooldown::...}`.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
If you're using variable-based cooldowns (the `{cooldown::...}` pattern), keep in mind that these are global variables. They get saved to disk and persist through restarts, which is great for long cooldowns like daily rewards but unnecessary for short ones like a 5-second ability cooldown. For short cooldowns that don't need to survive restarts, consider using temporary global variables: `{-cooldown::...}`.
If you're using variable-based cooldowns (the `{cooldown::...}` pattern), keep in mind that these are global variables. They get saved to disk and persist through restarts, which is great for long cooldowns like daily rewards but unnecessary for short ones like a 5-second ability cooldown. For short cooldowns that don't need to survive restarts, consider using ephemeral variables: `{-cooldown::...}`.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants