MON@H
-
Posts
389 -
Joined
Content Type
Profiles
Warranty Claims
Downloads
Forums
Store
Services
Downloads Plus Support
DOWNLOADS EXTRA
Everything posted by MON@H
-
Added `Refunds => Block Despawn If Base Is Damaged` (true) Message, probably, should be changed to something like "Base was damaged, unable to despawn" or something, to avoid confusions like this -
I'm currently working on refactoring of this plugin. Please, be patient and wait for new version. I hope "it will solve all problems". -
Возможно последняя версия заработает на том хостинге (если ещё актуалЬно) -
Can't reproduce the issue. Like I said before, if you want to get a fast support - don't use comments, create support thread and describe more details there, so I could reproduce the issue.
-
Hmm, this issue has never been reported before, I will check it and fix it soon Yes, it's in config called "Limit Total"
-
@Viktorvillif you want to get support - use support section and be more specific. All that described on description page is working. Plugin was tested many times. -
@MNfreakTim, if you are asking about this plugin data file - there is none. All data is cached in memory, so there is no phisical file you could read (Since this plugin was about maximizing performance). So if you need to trace all players builded entities, you should use some other plugin for that. This plugin was tested so many times that I can ensure you it counts correctly.
-
@Katze, yes, you can limit any entity by prefab name and yes, setting limit to 0 will prevent players from building it.
-
It is possible, to add this as an option, but I don't see no reasons to add something like this. Admin can easilly kill players using plugins like Slap or Player Administration
-
Well, actually, it's not a big deal to add a ban option, but, I believe you don't really need to do this. Reconnecting after each attack, as well as losing all items on death from slap, should be pretty annoying as punishment. Try it first and then tell me if you are not agree.
-
There is nothing to config in that plugin. You must edit data files of BotReSpawn and change to "Target_Noobs": true if you want to prevent bots from ignoring all your players. And I was talking about default value of BotReSpawn plugin. Since many people using this "No Sash" plugin, it would be wiser to set this default option to true. Also, for all people with "No Sash" plugin installed this new option will be entirely useless. It could be implemented some other, more accurate way, but that's the different story. -
Would be better idea to set this default value to "true" instead of making people search for this
-
Плагин 100% рабочий. Попробуйте обратитЬся в службу поддержки хостинга, или отключитЬ "GUI notification enabled": false
-
Performance was a top priority for me when creating this plugin. I can add custom groups, but it will take some time for coding and testing to make sure it doesn't impact performance. I am currently working on other plugins. Since this plugin is very stable and performant at the moment, I don't plan to add it anytime soon. Maybe later
-
The building limit for entities deployed on building blocks will not restrict entities placed on the ground.
-
No
-
@David Jackson, @dwwillia, added in latest version
-
Нет. Вот тут всё описано.
-
Да
-
Personally, I bought this plugin for developer support. Steenamaroo, with all these years of free development and support, you certainly deserve this support! To everyone out there I can also advise to think before whining about things you don't like here and there. You'd better ask yourself, what have you done to improve something? If you can still do something (like buy a plugin for developer support or do some debugging and help solve some problem, etc.) then do it, and if you can't, then at least , do not bring additional pain and frustration into life. to those who can.
-
Latest version is 1.4.2, make sure you update the plugin
-
NRE is fixed in latest version. Check it out and if you still have issues let me know
-
Found a typo. Fixed in latest version
-
Do you know how to reproduce it? I mean how can I reproduce this error in my environment? I have all checks and I just have no idea how are you getting those errors, if only I could reproduce it on my side then I could fix it. At this moment I'm comfused.
-
You must allow player to damage another player in TruePVE config file e.g. "anything can hurt players" or "players can hurt players" PunishAttacker will prevent damage instead on TruePVE.
