Rice Plugins

English

简体中文

English

简体中文

Theme

Handy2023-04-05
940
5.8m

FAQ ​

1. Where do daily random tasks come from? ​

Before version 1.4.1

The plugin performs a logic check every hour after startup (as long as today's daily task list has not been generated, it keeps checking).

  1. Tasks have been created.
  2. The task count in config.yml is greater than 0.
  3. Generate the daily task list, and assign the tasks to all online players.
  4. When a player logs in, they automatically receive the daily task list, players who already got it will not get it again.
  5. Daily random tasks theoretically refresh between 0 and 1 o'clock (if you have created tasks).
  6. You can use /plk getToday to trigger it once immediately, running it again will not grant tasks twice.

After version 1.4.1

The logic check runs at 00:00 to generate the daily tasks. After the initial setup you can use /plk getToday to trigger it once immediately, running it again will not grant tasks twice.

After version 1.6.0

Daily tasks are generated by a logic check at 00:00 automatically, drawn only from tasks whose type is everyday. Use /plk getToday with caution, this command clears the previous player task data and regenerates today's random tasks (it does not affect the task list you created). For performance reasons, all old historical task data is now cleared whenever new daily tasks are generated.

After version 1.11.0

Players automatically receive their daily tasks when they log in. At 00:00 yesterday's tasks are deleted and today's tasks are regenerated (drawn only from tasks whose type is everyday).

2. Can't the required items and reward items of a task be translated? ​

Version 1.13+ translates them automatically according to the configured language, all languages are supported, for example zh_CN, zh_TW and other locale codes.

How to configure:

  1. Change language: [locale code] in config.yml.
  2. Create a language file in the languages folder, named [locale code].yml.

Other versions are configured in item.json, just define your own entries in JSON format. Configured items are translated automatically, the rest are not, so please make sure every English word is spelled correctly (adding items here as you use them and then reloading the configuration file is recommended).

Example:

json
{
  "NAME_TAG": "Name Tag",
  "PAPER": "Paper"
}

3. Are mod items and custom items supported? ​

All custom items are supported, 90% of mod items are supported, a very small number of special items may not be supported, please test them yourself.

4. Custom commands for task rewards ​

  • The player runs the command, the 0 in the middle means run as the player, it fails if the player lacks permission: /plk addReward command 0 eco#give#${player}#666
  • The player runs the command, the 1 in the middle means run as OP: /plk addReward command 1 eco#give#${player}#666
  • The console runs the command, the 2 in the middle means run as console: /plk addReward command 2 eco#give#${player}#666

5. How to submit submit-type tasks ​

With the middle mouse button. Plugin version 1.12.2+ merged this into the left mouse button.

6. Clicking an NPC with a bound task does nothing ​

Please check the PVP status, world PVP being disabled or spawn protection and similar settings prevent the event from firing. If PVP cannot be enabled, you can use /plk openNpc [npcId] to open it directly (2.0.1+).

7. Not enough tasks after refreshing or after a player joins ​

Reason: the daily task count is too low. It is reasonable to set each rarity's task count to more than twice the total number of daily tasks. Normally nothing needs to be done, the tasks are completed automatically when the player rejoins.

8. Can the task shop have purchase permissions? ​

Not in the current version.

9. Can sub-servers connected to the same MySQL have different versions on a BC network? ​

No, inconsistent item data between versions will cause problems.

10. After upgrading, for example from 1.18 to 1.20, can I go back to 1.18? ​

No, you can only upgrade, you cannot downgrade.

11. This plugin has high database requirements ​

sqlite has low capacity, servers with more than 20 online players should use mysql.

12. What is the enchantment list for task objectives? ​

Click to view the enchantment list

13. What are the rarity permissions in the task config.yml? ​

Format: playerTask.rarity.[rarity type].[permission type]

Example:

  • playerTask.rarity.normal.default (every player has the default permission)
  • playerTask.rarity.normal.vip

14. What are the refresh count permissions in the task refresh.yml? ​

Format: playerTask.refreshNumber.[permission type]

Example:

  • playerTask.refreshNumber.vip1
  • playerTask.refreshNumber.vip2

15. Players get the same tasks every time they log in ​

Reason: the daily task count is too low. It is reasonable to set each rarity's task count to more than twice the total number of daily tasks.

16. How to configure custom menu command execution? ​

Custom buttons can be extended without limit, just follow the format of the example below.

  • command: "plm open menu" — execute the command as a regular player (recommended)
  • command: "[op] plm open menu" — execute the command as OP (not recommended)
  • command: "[console] plm open menu" — execute the command as console (recommended)
  • command: "[close]" — close the current menu
  • Note: ${player} represents the player name.
yaml
custom:
  # Back button
  back:
    enable: true
    index: 50
    name: "   &8[&aBack&8]"
    material: BARRIER
    isEnchant: false
    lore:
      - '&f- &7Click to go back'
    custom-model-data: 0
    # Command to execute
    command: "plm open menu"