- September 30th, 2019, 10:01 pm
#171711
Hey Hey! Let's talk about raiding.
As you all know, raiding is pretty much the only method to claim a building which has already been claimed by someone else (if you don't want to buy it off them or they won't sell it to ya.)
You call the raid, and this sets off a 120 second timer. Here's my issue with this.
#1. Players who have joined AFTER the raid timer was set off will not be aware of the raid until the "Raid has started" notification pops up, and if they are in the wrong place at the wrong time, well, Requiescat in pace.
#2. If you happened to be typing when the notification was set off, you likely wont see the notification when you press enter to send your message, due to the fact that any colored notifications which are sent on the server go invisible after you enter and exit the chat once.
Counter-argument to the first point:
"There is nothing we can do about this. It is unfortunately going to be on the fault of the player if they are within the area when they raid starts, whether or not they had joined after the raid timer or not."
This is incorrect in a few ways.
Firstly, you could always set the timer to alert at 120 seconds AND 60 seconds. Whilst there would still be people who get caught in the cross-fire if they joined after that second notification, it would cut down on a lot of the wrongful KOS calls by players who had just joined and had not been aware of the raid.
Secondly, you could definitely make the color of the raid text a bit more noticeable. Purple, of all things? It's something we already see a lot, and it has no "look at me, i'm probably something important" vibe. (I could be wrong about it being purple, I'm writing this off the top of my head, but whatever color it is, I've never noticed it and went "oh I should probably read that.")
Counter-argument to the second point:
"That is not something we can change. It's the plugin's fault, not ours."
My response:
This could very well be true, but if it is causing such problems, maybe you oughta rethink what plugin you're using? I respect the fact that it takes a lot of work to upkeep this server, but if such issues are occurring, perhaps you should look at the other issues it could cause? You might find that there are other issues which have been lurking in the shadows, less obvious than this one.
My goal in this suggestion isn't to cause mayhem, or to make people think I want only what's best for me; Because truly, I just want what is best for the server. I enjoy the conversations which are had, and if ya'll can keep it reasonable and not hostile, I'm down to have a discussion about it, and what we could maybe do better or not change; I'm not an expert, I'm just someone who's observations have brought me to type out this (semi-long) suggestion in the hopes that someone more understanding than me on the situation could add-on, or make an argument towards it.
Thanks for reading!
As you all know, raiding is pretty much the only method to claim a building which has already been claimed by someone else (if you don't want to buy it off them or they won't sell it to ya.)
You call the raid, and this sets off a 120 second timer. Here's my issue with this.
#1. Players who have joined AFTER the raid timer was set off will not be aware of the raid until the "Raid has started" notification pops up, and if they are in the wrong place at the wrong time, well, Requiescat in pace.
#2. If you happened to be typing when the notification was set off, you likely wont see the notification when you press enter to send your message, due to the fact that any colored notifications which are sent on the server go invisible after you enter and exit the chat once.
Counter-argument to the first point:
"There is nothing we can do about this. It is unfortunately going to be on the fault of the player if they are within the area when they raid starts, whether or not they had joined after the raid timer or not."
This is incorrect in a few ways.
Firstly, you could always set the timer to alert at 120 seconds AND 60 seconds. Whilst there would still be people who get caught in the cross-fire if they joined after that second notification, it would cut down on a lot of the wrongful KOS calls by players who had just joined and had not been aware of the raid.
Secondly, you could definitely make the color of the raid text a bit more noticeable. Purple, of all things? It's something we already see a lot, and it has no "look at me, i'm probably something important" vibe. (I could be wrong about it being purple, I'm writing this off the top of my head, but whatever color it is, I've never noticed it and went "oh I should probably read that.")
Counter-argument to the second point:
"That is not something we can change. It's the plugin's fault, not ours."
My response:
This could very well be true, but if it is causing such problems, maybe you oughta rethink what plugin you're using? I respect the fact that it takes a lot of work to upkeep this server, but if such issues are occurring, perhaps you should look at the other issues it could cause? You might find that there are other issues which have been lurking in the shadows, less obvious than this one.
My goal in this suggestion isn't to cause mayhem, or to make people think I want only what's best for me; Because truly, I just want what is best for the server. I enjoy the conversations which are had, and if ya'll can keep it reasonable and not hostile, I'm down to have a discussion about it, and what we could maybe do better or not change; I'm not an expert, I'm just someone who's observations have brought me to type out this (semi-long) suggestion in the hopes that someone more understanding than me on the situation could add-on, or make an argument towards it.
Thanks for reading!
"It's a bird, It's a plane! oh wait.. its just Bird."
RP Player since 2018.
Idiot since birth
RP Player since 2018.
Idiot since birth