TheZZL

Told you boys you’d get it @CptFlynt @Nate. Grats to the rest! @Strayyz climbing the ladder up @Benzene online school tutor

good enthusiasm event coordinator THE EVENT IS LATER TODAY, BE THERE OR SQUARE! LAST FEW CHANCES TO GAIN FREE PONITS FOR THE LEADERBOARD CONTEST

@Starlegendgod We need you for this one

You've just responded to a three page thread about the change you're talking about, please do a little bit of reading: Not only do you have BOARD MEMBERS flat out telling you the reason why, there's discussion from said higher staff and regulars on this topic. Just...

Answered here: "Actively knife the ground" and "Knife the ground" are two distinct orders, one is ordering you to continuously do an action while the latter says to do a singular action. To actively be doing an action is not implied, however you should do the order as stated. General good practice is go be as clear as you can be with your order, so if it means blatantly saying what you want them to do you should be doing that.

@Dominic waiting for you to come back, overthrow the REAL tyrants, and give me Legend.

Only watching if @kabLe casts/captains a team

Excited for this, hopping on right now!

I answered your post, for the second question, yes if it's the same person breaking rules make one player complaint for them. If in your clip you have multiple people breaking rules you can make one player complaint and timestamp it and include all their STEAM ID's. Just include however much evidence you have, a CA will look at the footage and determine a punishment. If it wasn't clearly @dafty pal, I do have actual authority.

How about no nuke, and just move on. Also if these clips are from a month+ ago they will likely be rejected anyway. Focus on going on Jailbreak and making fun of children Better yet, dafty applies for admin and bans the rulebreakers himself???????

I just read this part, This is absolutely not the right way to file a player complaint, coming from me. If you have bannable footage (Mass freekill being a good example of one) submit a player complaint, dropping a "nuke" player complaint will get the team to loathe you and probably deny your complaint unless you have timestamps. Save yourself, and the team, a headache and just post them as they come.

This is roughly right in my opinion. There's no guide in the CA section saying if the reported player freekills three people ban them, but 3+ is a good number to go by. Also remember that factors like their playtime and intent play a big role in whether or not it will get rejected; If it's a new player who accidentally freekilled or just made a mistake, they might get an easier punishment or none at all.

It's not KOS, incorrect ruling.

We discussed it, and moving the healthboost to the front page would basically replicate a bind, which is not something we want. The current order of the Buy Menu is alphabetical, and it's fine how it is. You're not meant to lean on the healthboost as a crutch during fights, you should ideally be using it before/after the fact, but what the developer intends doesn't always match with what the user does. As for a T Menu/buyables, not happening, read the linked post in my previous response here.

We've made some slight changes to the map that should help the Guards out, but I recognize this map is harder to play on for our server. If it continues being difficult we can discuss removing it. So for now, we'll be rejecting the request, but I'll leave it open incase people want to continue discussing.

2/27/21 Small changelog for today, Balance changes to jb_quake_a04d to make the map bearable for the Guards Removed the Bizon near Surf Replaced the M4A4 by the water with a Deagle Made the breakable secret near Deathrun stronger, meaning it'll take longer to break from now on Added a chat & name filter for obscene racial slurs It'll replace these slurs with [Bad Word], if you see any mistakes with this please leave us a Bug Report!

Hell yeah! Cool rewards BR, thanks Oh and uh...

Stop dissing JB

The rules clearly state, When taking the First Order Guards must give their order, and that's it. Admins will usually let players get away with talking as long as they're giving an order and being clear. Taking !fo to shit-talk and not give orders is not allowed. As for increasing/decreasing !fo time, once there are 30 players online !fo extends to 45 seconds instead of 30. Decreasing !fo time, like others mentioned, is just another slight nerf to CTs. When you take the First Order you can lead the round, and extend your one order into the next couple of minutes depending on how you use your time and speak. I suggest anyone that takes First Order understand you're shaping how the round turns out and leading it, so if you need guards in a position to support the order you're about to give, ask them to get situated in a spot that convenient for you and the order. We will not entertain the idea of allowing Guards to not give warning shots during First Order, as it's not only confusing but also can open up more conflict and problems. Thanks for the suggestion, i'll leave the thread open in case you or anyone else wants to respond.

The LR Plugin was initially meant to be updated in the fall, but we got sidetracked with other projects so we put a pause on it. We've gratefully asked @Cept For Her to continue working on it again, and the new version will include bug fixes, new LRs, and general improvements. If you have any ideas feel free to put them here, but we've got a decent number of new LRs coming. I can't tell you when it's coming as that's up to Cept and his busy schedule, but expect it in the next couple of months? Cept what you think.

I've got some fun stuff planned in the coming months, sit tight, we might also go with a different RTD Plugin as the current one has some bugs. We'll see, stay tuned.

The event was a lot of fun! We didn't get that far on cyberpunk but cursed bear was good, thanks for the event guys.

Hey dafty, I think you'd really like these these two songs! let me know what you think!

It's both cheating the LR and an exploit. You're not intended to do this at all, we'll be fixing this in the V2/update of the LR Plugin.