MeventSupport
-
Posts
1,676 -
Joined
-
Last visited
-
Days Won
8
Content Type
Profiles
Warranty Claims
Downloads
Forums
Store
Support
DOWNLOADS EXTRA
Services
Everything posted by MeventSupport
-
To do this, you don't need to change LangRu to true in the plugin code, but leave the default false -
Please can you send config and data files -
It's just a warning, you can ignore it -
The algorithm is set up in such a way that it doesn’t. If you want rewards not to be given out immediately, enable the reward inventory — this will allow rewards to be sent to a virtual inventory and claimed at any time. (The inventory can also be automatically cleared during a wipe.)
-
Hello! Unfortunately, the Stacks plugin cannot handle individual item skins - it only works with item types. The G1 grenade from Nades Plus is just a skinned F1 grenade, so it will follow the same stack size as regular grenades. Solution: Use the console command: stacks.manage stack set grenade.f1 [stack_size] This will affect ALL F1 grenades including your G1 grenades. The plugin currently doesn't support different stack sizes for different skins of the same item type.
-
Yes, we know about that, thank you very much! We are trying to finalise V2 to release it!
-
Yes, we know about that, thank you very much! We are trying to finalise V2 to release it!- 328 comments
-
- 1
-
-
- #building
- #foundation
- (and 27 more)
-
1. Check your "Loot Settings" configuration - make sure "Enabled" is set to true. If it's disabled, no points will be calculated even though stats are still being tracked. 2. Verify that your loot items have scores assigned in the "Loot Settings > Loot" section. If all items have 0 score, players won't earn any points despite their actions being tracked. 3. Try enabling "Debug Stats" in your configuration to see if stats are being updated in the console. This will help identify if the issue is with tracking or point calculation. 4. Check if your loot configuration has the correct item names and loot types. If items aren't properly configured, they won't award points even though the actions are being recorded. 5. Restart the plugin to reload the loot score cache. Sometimes the point calculation cache needs to be refreshed after configuration changes.
-
These are errors from the NPCShop plugin, UltimateLeaderboard has nothing to do with it
-
We want to assure you that we are working on resolving your issue. Due to a high volume of requests, the processing may take a little longer than usual. Thank you for your patience and understanding!
-
.
-
Make sure you edit the "Deposit Fee" and "Withdraw Fee" in the config’s "ATM Settings" section, then reload the plugin. Changes in data files alone won’t update the tax.
-
Fixed -
The issue is with the scroll height setting. In your popup configuration, find "Scroll Height" and set it to a higher value to accommodate all your commands.
-
Hey! To help properly, could you: Show where you're using API_SegisterEvent (screenshot/code) Explain what you're trying to achieve? Example: "I want to register events in offline mode"
-
I will add this
-
Could you send the video?
-
Hey! Try updating the plugin. If it doesn't help, record a short video and I'll see what's wrong.
-
Hi! Install ShopConverter on your Rust server, then use console commands 'shop.convert.sr' or 'shop.convert.shopui' to convert data files—it handles default paths automatically.
-
Hey! That might be a typo — did you mean API_RegisterEvent? Can you give me more details so I can help fix this issue for ya?
-
To switch to direct items, open your event config file, set "Put the reward in the MultiEventsInventory?" to false, delete the "Award IDs from MultiEventsInventory" lists, and add your items directly under "Awards".
-
The "already active events" messages occur because EventsManager tries to start events that are still running from previous sessions. Each event plugin protects itself from duplicate starts. Quick Fix: - Open /em and increase the intervals between your events - Add random offset delays (5-15 minutes) in your time settings - Ensure your intervals are longer than your events typically run This prevents timing conflicts while keeping automatic scheduling working properly. Best regards
-
Yes, mates, we already know about it! We're thinking now, as a team, what would be the best way out
- 328 comments
-
- 3
-
-
- #building
- #foundation
- (and 27 more)
-
Can you please send the video
-
hello, I’m sorry I didn’t reply for a long time. Lost your message Check your event schedules in /em - increase the interval between events and add random offsetMin/offsetMax delays to prevent timing conflicts. Short intervals can cause events to interfere with each other.