Jump to content

Golden Pup

Member

 Content Type 

Profiles

Forums

Events

DarkRP Server Rules

Forum Rules & Guidelines

DarkRP Server Rules (Compat Test)

rules-compact-manual

Posts posted by Golden Pup

  1. I am SO glad you made this thread.

     

    Here is my take on LTAP: the term LTAP should be reserved for special cases, I feel it is grossly overused. 

     

    In order for the term LTAP to be included in a ban report one of two things should have to occur.

     

    1) the user in question clearly and excessively breaks the rules and then disconnects (i.e. mass RDM, mass RDA, Server threats, etc.)

     

    2) the user in question is brought to a sit, upon being teleported the user recognises they have been brought to said sit and disconnects immediately.

     

    I feel these are the only two instances in which LTAP should be a viable addition to a ban report, in any other case there is plausible deniability. We as staff can't prove the user left to avoid punishment, and the user can't prove that they didnt. It winds up landing in a "grey area" which makes it difficult and to be honest annoying to reach a clear verdict. 

     

    This is my own opinion however, someone else may see it differently.

     

    It's kinda like NITRP in how often it's used.

  2. I mean, it's highly situational. If it's obvious in the logs and shownlr that the guy, say, revenge RDM'd and then left a second after the kill happened...

    On the other hand, "he didn't mug me right!1!! :@ " and the guy left like two minutes after it happened, yeah.

    Just use your best judgment.

     

    What about the people that use "AFK is a form of LTAP"

  3. Banning for LTAP is so hazy unless it happens directly infront of you. When a sit sits there for awhile, the person may leave just because they have something come up or want to get off for the day. Another thing about LTAP I've come to dislike is that going AFK is a "form of LTAP." Just some little thoughts I've had on this topic. Would like to hear more opinions on banning for LTAP and what should be considered as actually leaving to try to avoid punishment.

  4. Terrorist should be the Bin Laden we see in the loading screen. that would be cool


    as for not seeing info through props, it's because you're looking at the prop.

     

    It like text screens, if placed over a world glow prop its hidden. The bad thing is when every base in crowded areas has world glowed props. I think the best fix is either what dima said, or make them glow like revolts.

  5. Bug

     

     

    Description: The indicator for terrorist does't show over world glowed props. The indicator being so annoying hard to see and not being able to be seen over world glows props makes it lead to a lot of people assuming RDM. (That combined with terrorist looking like black market dealers)

     

    How to reproduce: Position the indicator over a world glowed props

     

     

    Priority: Medium-High

     

     

     

  6. A rule should be added for people making sits about if they have no sound they should either make it where they can hear us or just not make the sit. If they could hear people over voice chat when they get RDMed/ whatever it is that happens to them, then they might not have made the sit to begin with. Also making a staff member and the another person in the sit type makes for longer sits, and if the server is full or near full, that can lead to a lot of back logged sits.

  7. I had a suggestion that I sorta brought up in the server meeting. 

     

    Impliment a new policy on battering rams. Instead of making it so props are unfrozen, it should ghost props for say 3 mins, INCLUDING Fading doors/

     

     

     I think 3 mins is fair, as it gives enough time for a raid BUT not so much that it prevents a player from returning.

     

    Reasons: People spend hours making a base, why should they have to start over

                   It would be nice not to get killed by props when raiding.

                   It would make bases, slightly, more raidable

     

    I actually agree with this a lot. It's annoying when you make a base then a cop warrants you and destroys the whole base and you have to remake it. It's even more annoying when you're not staff or VIP so you can't save it then all of that work is wasted and you just get salty. Plus, CP proof doors are very strong cause of the reason of you cant battering ram it fast enough and usually cops dont always work together in raids. I dont think it should be 3 minutes though. I think it should be more of 20 seconds because the speed that the battering ram destroys props and the amount of cops that might be there with battering rams. But, other than that, great suggestion!

    The problem with 20 secs is the like 52 part fading doors

    or the 700 props stacked on one another

    Cops aren't supposed to raid alone, i.e. the call for back up system, so if there is 5 cops raiding one base and it lasts 3 minutes, well its not gonna take long for 5 cops to get through, not really fair for the base owner, it needs to be less than a minute at minimum.

  8. I know you just added  but PLEASE get rid of the new staff notification module. There are too many staff on during the day, especially with the new tmods that it's not effective. It honestly just serves as an annoyance. I can't even thoroughly get through one sit without it going off and distracting me from the task at hand.

     

    In theory and on paper it was a good idea. In practice it's a bit of a nuisance.

     

    It's especially fun when you're the only staff on for hours and handle all the sits, and then another staff comes on and you finally think you're gonna get a break and then BEEEEEEEEEP BEEEEEEEEEEP

     

    at the very least code it so that it deactivates when there are more than say 3 staff on.

     

    "If playergroup.staff >= 3

    Then timer.adminmodule =off"

     

    easy fix, make it go off after 15 or 20 minutes of not taking a sit, rather than 4. You can't even actually do a sit without it going off. If that's not annoying enough to get our attention it could go off every 5 after that, adding more beeps like it does.

     

    You could also have it stop counting if no sits have come up in x time, or more than x staff are on

     

     

    You legit can't role play for once without it annoying you to the point of logging off

  9. I know you just added  but PLEASE get rid of the new staff notification module. There are too many staff on during the day, especially with the new tmods that it's not effective. It honestly just serves as an annoyance. I can't even thoroughly get through one sit without it going off and distracting me from the task at hand.

     

    In theory and on paper it was a good idea. In practice it's a bit of a nuisance.

     

    It's especially fun when you're the only staff on for hours and handle all the sits, and then another staff comes on and you finally think you're gonna get a break and then BEEEEEEEEEP BEEEEEEEEEEP

  10. Make raid cool down timer longer than 20 minutes it feel short when players b2b raid you on the second of the cool down for a long time. I was thinking maybe 30 min even

     

    The whole purpose of the 20 min cooldown is for the people that got raided to improve their base, fix what allowed the raiders to get in, if the raiders go back after 20 min and its unaltered, then 30 min wouldn't even help them

  11. If I hear that song I:

    1. Inform party members

    2. Book it the heck away from my stuff

    and 3. Get ready to shoot him when he appears

    Not any reason to get rid of the job considering you have probably a good 20 seconds to do all this.

×
×
  • Create New...