- February 18th, 2016, 9:59 am
#4207
When you say timed raids, how much do you think is adequate time for a raid? The drawback is if the raiders can't get to the loot in time, due to a large base well fortified (many doors and walls), there is gonna be a lot of bitching about how long the raids should have. "Oh it wasn't enough time! It needs to be longer!" Or the flip side "The Raiders have WAAAAY too much time! Make it shorter!" And who exactly is gonna time these raids? I mean yeah, if a mod is on, the raiders could call a raid and mod goes on duty, tp's to the raid caller, and times it. In world chat the mod could give them some idea when it's gonna be ending soon so they know to start backing off if they haven't finished. Any raiders still in the base can be considered breaking the timed raid rule.
As for the lives, that is gonna be hard to tell until the end of a raid because no one is gonna want to stop during the raid to complain about so and so still going to the base when they shouldn't be there. That would cause a waste of time, if there still is the timer on the raid. As the rules indicate, raiders can keep going to the raid until they ALL die, meaning all of them at one point and time, none of them in the base. (Which should be part of the raid rules, all raiders have to be INSIDE the base, no guy on the outside of the base accepting TP's being anchor for anyone that dies) As for defenders, they can keep going to the base as long as they have their bed there. Keep in mind people, there is a /TPA timer that is pretty long to help control on /tpa's to raids. /home timer could be extended the same amount if people really feel there should be a limited life system.
Another thing to note would be when declaring a raid, it should say something like "Ark group raiding base near Seattle" or if they have someone helping, "Ark group with so and so, raiding base near Seattle" This way no one can join in to help raiders in the middle of the raid. Any other people helping a group raid can be accountable for breaking raid rules.
I agree, there should only be one raid at a time, to clear confusion.
Another thing to add would be, whomever calls the raid, has to declare it's over. This way no one else in the raid group can say it's over when they aren't all ready to call it over. This will clear confusion on if the raid is really over or not. But as soon as that person declares it's over, that's final, it's over, no take backs. Any kills after that point should be considered KOS. No matter who kills who. (defender killing a raider right after they declared it over or vise versa) At that point they should all go on their ways, Normal RP resumes.
I will admit, Raiding yesterday turned into basically Wars with some sort of rules. It seemed like a killing field. And there was a lot of confusion about the lives rule. So I would like to say, I believe any raiding group declaring a raid should be responsible for actually reading the rules that day to make sure they ALL know the rules. So when they declare a raid, they're ALL agreeing that they read the rules that day. Meaning if any of them break a new rule that was implemented, that one person that broke a rule, is to blame for not being up to date on the rules, aka not reading the rules, and should be accountable for whatever rule they broke. Actions against breaking said rules like that could be a warning system, too many warnings and they get a ban. If a mod catches that person breaking a rule during the raid, they can kick them, reason "Not knowing the rules, go read them. Warning 1" or something like that.
I have a YouTube Channel now. I do a lot of hunting with friends, running around having fun as LAPD Popo, Kill montages, War videos and other random videos. Don't be afraid to stop by, give some comments, subscribe, whatever lol.
Arashi"TheWolf"onYouTube