Markers and other stuff

I use a this plugin on custom maps. It's often very hard for my players to meet the requirements of a raid due to the massive amount of unconfigurable restrictions you've placed on the starting conditions. Can you please at least make them options we can turn on and off? This plugin is mostly useless to my players now. Even a map marker a square away prevents a raid.

18 hours ago, Harley Ross said:

I use a this plugin on custom maps. It's often very hard for my players to meet the requirements of a raid due to the massive amount of unconfigurable restrictions you've placed on the starting conditions. Can you please at least make them options we can turn on and off? This plugin is mostly useless to my players now. Even a map marker a square away prevents a raid.

Most of the conditions that are blocked create bugs or ways for players to easily win a raid.

Just to make sure, are you aware you and players can run a command at any time as they are building their base to make sure it's able to run the event? I wanted to ask that first.

After that if you can give some specific suggestions on what restrictions you would like to turn off I can add them to our notes.

I would like as many options as possible. I think it should be up to the server owner if they want the raids to be easier or not. Thinks that cause errors I can understand. But like I said, I have several players that cant start a raid for seemingly no reason. Big open areas lots of space, they try the command to check, but there are so many restrictions, there are few places on a custom map that qualify.

Monument markers seem to be the biggest issue so far since custom build areas are marked on the map making the majority of my users not able to use the plugin. 

Also now I'm having reports of users with 3000 hours of cooldown. Despite me not having changed anything.

11 hours ago, Harley Ross said:

I would like as many options as possible. I think it should be up to the server owner if they want the raids to be easier or not. Thinks that cause errors I can understand. But like I said, I have several players that cant start a raid for seemingly no reason. Big open areas lots of space, they try the command to check, but there are so many restrictions, there are few places on a custom map that qualify.

Monument markers seem to be the biggest issue so far since custom build areas are marked on the map making the majority of my users not able to use the plugin.

Also now I'm having reports of users with 3000 hours of cooldown. Despite me not having changed anything.

It is not just a matter of making raids easier, as many of those instances create errors when the NPCs cannot navigate in certain areas. There was feedback and testing taken into consideration during the plugins development and early versions. Configuration allows raids to be made easier or more difficult. If something is blocked then during testing and or feedback there was a reason for it.

There is never not a reason that players cannot start a raid. Players can run the command while placing the initial foundations if they want to run raids there, or they can find places to construct small bases just to run the event. The command can be run during construction once a TC is placed as well as checking after it is complete if the event cannot run, to see what areas are affected. There is a guide in the Description for what the different symbols mean.

In regards to the cooldown, unload the plugin, delete the DefendableHomes file in your servers data folder, and load the plugin again.

Additionally if the map markers are not desired, maybe this particular issue can be considered and made configurable, I will ask about it. Alternatively as well you can ask the map developer to remove them, or remove them yourself in RustEdit. Currently it is in a beta version as a note.

I make my own maps. I will not remove much needed 30ish map markers my players need to find custom build areas.

I would much rather use a different plugin that doesnt have all the restrictions. I would not let 1 of my 100 plugins dictate what I can and put on a map.

If you can make an option to ignore map markers this plugin may still be useful to me. If not I'll have to ditch this plugin as useless and find another.

I'm just trying to salvage this plugin I paid for and my users want. Not sure why it would be a problem to add an option for ignoring map markers. Other than maybe the seller of the plugin is not the creator of the plugin.

Checking while you build is a bad idea for a solution. Players dont have the time and resources to waste, building something that almost always fails.

I just want to be able to use this plugin I paid for.

Double post sry

26 minutes ago, Harley Ross said:

I make my own maps. I will not remove much needed 30ish map markers my players need to find custom build areas.

I would much rather use a different plugin that doesnt have all the restrictions. I would not let 1 of my 100 plugins dictate what I can and put on a map.

If you can make an option to ignore map markers this plugin may still be useful to me. If not I'll have to ditch this plugin as useless and find another.

I'm just trying to salvage this plugin I paid for and my users want. Not sure why it would be a problem to add an option for ignoring map markers. Other than maybe the seller of the plugin is not the creator of the plugin.

Checking while you build is a bad idea for a solution. Players dont have the time and resources to waste, building something that almost always fails.

I just want to be able to use this plugin I paid for.

First let me just clarify that KpucTaJl develops plugins and I provide support for him. We are a team. Then although I already explained it, I will again explain that these things were blocked with reason and in response to customer feedback and issues that arose. As I stated in my previous response the developer may be willing to and interested in adding some configurable options, but it does depend on the situation. Some things are blocked or removed for a reason but it can certainly be discussed. Nobody ever said it was a problem.

The one thing I will say though is that checking while building is a good idea. I see no argument for it being a bad idea. If players don't have time and resources to waste, then checking early is a great idea. This is always going to be the case regardless of if certain things are given a config option, some things will always be blocked and if players don't check until after they've finished the entire base then they would be out a lot more in time and resources to make another base or make changes to the current one than if they just check as they are building. This is not an issue for countless other customers and their servers. The plugin has been purchased over 250 times just on this site.

You can use the plugin you paid for, and the last thing I want to point out is that plugins are as they come. It's fine to give feedback and make suggestions, but try not to jump conclusions or make demands just because you want something a certain way. I am not trying to be dismissive, argumentative, or anything like that. I was simply explaining why the system was in place and that it has reason.

I will go ahead and add a note for this plugin and reference the ticket. The developer will take a look, consider it, and if needed might reach out if he has any questions.

And I've told you I understand for those things that do cause actual errors in the code.

All I am asking is for a reasonable solution to my problem with your plugin. 

I'm not asking you to rewrite it, I'm not asking you to change any default options or settings. I'm asking for an option to ignore some of the restrictions. Put a warning in them or whatever I dont care. I just want to be able to use the plugin. I'm not asking for anything  unreasonable.

Thanks I guess. At least now I know what plugins to stay away from.

3 hours ago, Harley Ross said:

And I've told you I understand for those things that do cause actual errors in the code.

All I am asking is for a reasonable solution to my problem with your plugin. 

I'm not asking you to rewrite it, I'm not asking you to change any default options or settings. I'm asking for an option to ignore some of the restrictions. Put a warning in them or whatever I dont care. I just want to be able to use the plugin. I'm not asking for anything  unreasonable.

Thanks I guess. At least now I know what plugins to stay away from.

And I've told you that you are asking to unlock things that do cause actual errors.

I feel like I have been completely reasonable in explaining the situation. Maybe a reasonable request gets a reasonable response?

I explained that I don't write the plugin, it is not MY plugin, KpucTaJl wrote the plugin, and I do support for him. I told you that I added an entry to our notes and referenced the ticket. The plugin is usable. The only person deciding things are unreasonable or not is you. All I have done is explained WHY it is currently set the way it is and has been for quite some time now without issue.

You are welcome, I guess. At least I know that explaining things doesn't really help because you apparently are not even reading my responses. The note is there, not sure what else to say. The developer reviews the notes and references regularly.

Thanks for passing along the info. I've gone ahead and edited the plugin myself. I've removed most of the restrictions and it is exactly what I needed. There are no errors. 

I would like to see future versions with optional restrictions. I cant be the only person who could use this. For now I guess I have to edit the plugin myself.

We can't know how many people who want something unless they let us know. But I added the note.

Have fun with it!