Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 04/09/2024 in all areas

  1. It should be a separate punishment that's more severe then failrp + ltap as leaving to avoid a raid or to stop your printers from being taken is a lot more of a severe crime then just generic failrp, such as running into spawn to avoid a hit, then leaving the game which is just failrp + ltap. This is where I disagree and think this could use some work. FailRP is when someone is known to be punished and decides to leave the game in attempt to try to avoid it. That's when a FailRP is escalated to FailRP+LTAP. FailRP+LTAP is already at a 1 day ban, which is not very severe but still a measurable ban coming from a Warn w/4-6 minute jail. Now we get into Raid Logging. Nobody likes Raid logging, it's the worst part of DarkRP, and I think anyone who's pulled off a raid has had this happen to them. It's not fun to pull off a raid, the player leaves, and you have nothing to show for your sweet success. However, I don't think we should be enforcing a ban more severe than 1 day for somebody who leaves the game because they're defeated. No Intent to RP? Well, that case could be made. They had no intent to roleplay losing defending a base, or otherwise were mad enough that they left the game. However, this would be difficult to implement. Sure, the logs show that someone was raided, and that they died, and then that they disconnected - but is there any way to prove that the person actually left to avoid their printers being stolen? Even a video of you raiding the base, killing someone, and then they leave the server would be a bit iffy if you didn't know if they even had printers or anything valuable inside. I think if we're honest about this and how we'd proceed with actually punishing this, it's clear that this is not something the staff team has in the past ever wanted to deal with and not something to easily define a rule around. Say I'm a player, I join, I get raided. Am I now supposed to remain on the server for 5 minutes after I was killed in the raid before I'm allowed to play something else? 10 minutes? Am I held hostage now in the GarnetGaming server as someone milks my printers? Am I only required to stay until someone decides to claim my prints (taking up to 10 minutes on their raid as allowed)? I think the community mostly agrees that it'd be nice to have a rule in place to either prevent or at least punish and curb this behavior from continuing. But I don't see a good suggestion on what the actual rule is, or any punishment that I can agree would be fair for the crime of leaving the server after you lost. Really, the best way in my opinion would be to have someone's entities remain on the server for ~2 minutes after they disconnect, giving anyone a chance to fight over remaining printers, get some claims in, etc. This would prevent there needing to be a rule followed or any stricter guidelines placed on players that won't get followed or consistently enforced anyways. But since I don't know how hard this would be to implement or any exploitation risks involved, I'll just leave my wall of text here for the next person bored enough to read my thoughts. Until the community can come up with a fair: Rule for this scenario and Punishment for this scenario, for this I will remain Neutral.
    1 point
  2. Just got my Motorcycle Permit eyyo
    1 point
  3. Description: The year 1812, and you have been selected to participate in military duties. The stampede of colony: Garnet Dark Rp. A British or American soldier in these parts of town? Hello, sir? However, lest you push him to his limit or witness unpredictability within personal misfortune. The power of flintlock ball of steel, or the cutless of the life, I believe comradery and numbers make them strong to socialize. Therefore, a standard of rules need to be implemented. Perhaps even a pirate seems to wander the street with his blunderbust and wanderlust for crime. A sword by his side, he rides the sea, streets, and intimidates with his stature.Reasoning: ʸᵉᵃʰ, ᶦᵗ ʷᵒᵘˡᵈ ᵇᵉ ᶜᵒᵒˡ ᵍᵘʸˢ Additional Information: [Photos/Videos][/CODE] https://steamcommunity.com/sharedfiles/filedetails/?id=2827416571 * A bad pirate https://steamcommunity.com/sharedfiles/filedetails/?id=156923796 * Or a good pirate OR https://steamcommunity.com/sharedfiles/filedetails/?id=1479670913 * 1812 Soldiers With https://steamcommunity.com/sharedfiles/filedetails/?id=520596630 * Weapons Now, I am not proposing all this all to be added. Perhaps one or the other, or just one. I believe this would be neat, lads. (I vote for a Pirate job)
    0 points
  4. -1 that would be way too much to add to the server making it have more download time and not so much a vanilla server. Plus, it makes no sense to add that to the server. pirates maybe since there might be a sailor class but the British vs Americans doesn't fit the server, might as well make a server called 1812 and add those. Also, you have no strong reasoning supporting why this should be added.
    0 points
  5. +1, this is a good suggestion. It should be a separate punishment that's more severe then failrp + ltap as leaving to avoid a raid or to stop your printers from being taken is a lot more of a severe crime then just generic failrp, such as running into spawn to avoid a hit, then leaving the game which is just failrp + ltap.
    0 points
  6. +Rep Usually, unless mom says it's time to get off of the computer or you're having a dire emergency (which I don't see why you wouldn't leave your game open anyways, unless there was a natural disaster), it might be the case of an LTARD. Leaving To Avoid Red Dragon, also known as GG Code of the Life Momentum bill, 339-B. It's been decided in the courts that a pump action shotgun cannot be used to be played Imagine Dragons in front of the court house. Sorry, that's code Green Dragon, 339-A. In short and of the code, you shouldn't steal books from your local library unless you are a book thief.
    -1 points
This leaderboard is set to New York/GMT-04:00
×
×
  • Create New...

Important Information

Terms of Use | Guidelines