๐Ÿงช
Lee's Plugins
  • Information
  • ๐Ÿ’”Lee's Lifesteal
    • ๐ŸชงBranding Wizard
  • ๐Ÿ“‹TaskedUltimate
    • ๐ŸŒณGetting Started
    • โŒจ๏ธCommands
    • ๐Ÿ”ŒPlaceholders
    • ๐Ÿ“„Configuration
    • ๐Ÿ”˜Actions
    • ๐ŸŽซUnderstanding IDs
    • ๐ŸŽš๏ธDatabase
    • ๐Ÿ’ฌDiscord Integration
    • ๐Ÿ’ŽUpdating
    • โ“Why Premium
  • ๐Ÿ’ŽBlockEffects
    • Commands
    • Particle List
    • Particle Flags
    • Tutorials
    • Configuration
    • ๐Ÿ’ŽBlockEffects (Pre-4.0)
      • Commands
      • Particle Types
      • Modification Flags
      • Configuration
      • Examples & Usages
    • ๐Ÿ’ŽBlockEffects (Pre-3.0)
      • Commands
      • Particle Types
      • Modification Flags
      • Configuration & Storage
      • Examples & Usages
Powered by GitBook
On this page
  • ID Explanation
  • ID Location & Example
  1. TaskedUltimate

Understanding IDs

A quick overview of how a "task ID" works.

ID Explanation

A task ID is a unique number that is represented for each task. The reason each task needs a unique ID is to not only simplify the user needing to type their whole task out in a command, but to differentiate tasks that are the same, that way duplicates and such work without bugs.

ID Location & Example

A task's ID can be found by using "/task list <player>" and can be used in other commands like "/task complete <id>". For example, imagine I have created my first task for a player named "John" and John finishes his take, he can now mark it complete using "/task complete 1" instead of typing out his full task to mark it as complete.

PreviousActionsNextDatabase

Last updated 2 years ago

๐Ÿ“‹
๐ŸŽซ