Dominic

The order is completely valid and there is nothing wrong with shooting into isolation to enforce that order. If the CT shoots someone who is actually obeying the order, they'll get slayed. If the CT instantly kills a T who isn't on the back wall but is instead a step or two in front of it, they should also be slayed because that is not blatantly disobeying at all and a warning shot needs to be given. My advice would be to just not shoot blindly in any case, but that's just my advice and is not a rule whatsoever. The CTs are allowed to do what they're doing, but they'll face the consequences if they end up doing something wrong. EDIT: To clarify, when I say someone should/would get slayed, I mean they're doing something wrong. What they're doing is retarded but obviously as an admin you don't always have to resort to a slay.

4/16/19 First Order has returned and is better than ever! - !fo can only be used for the first 15 seconds of the round. Once used, you have 30 seconds to speak. After you use it, you have to wait 2 rounds before using it again. - Dead players should no longer be able to speak on their mics. - CTs are no longer muted on the first round of each map. Everyone give a huge thanks to @BoTo for this! He's worked extensively with us to complete this and push this out onto the server. Bugs may occur, so please report them in bug report thread. As always, thanks for being patient with us while we worked on this. Oh yeah, by the way, April 19th. Enjoy the server, ladies.

Congrats everyone! Excited to work with you, boys. @Metal @Kirby @ThRza

4/15/19 - Added new rule: CTs cannot obstruct a T's ability to follow the orders. Subject to admin discretion. - Added cvars: sv_ladder_scale_speed 1, sv_clamp_unsafe_velocities 0 (Thanks @Darnias) - Added new HDR maps that will improve a plethora of things, this is an ongoing project that @Darnias is working on. So far we've added an HDR version of vipinthemix and summerjail. More are on their way and this will be fully explained with a completed list in a future change log. - Added new plugin that still includes our !ma command which mutes all alives players but now also includes an !md command that mutes all dead players. - We had temporarily removed SourceComms from the server due to a bug, but now it's back online. Admins can once again issue communication bans on players. We will have a fix out to the first round CT mute bug extremely soon and First Order will also return shortly. We also have a very exciting plugin addition on it's way that we believe a lot of you will enjoy. Please be patient as we implement these changes and thank you all for your continued support through these issues.

So we're going to add a rule in because there is a lot of potential for a situation like this to become an even bigger problem. This may or may not apply to the situation that happened, I have no idea, but it brought up a much larger flaw within our rule set that we want to amend here and now. Here is the rule we're adding in: - CTs cannot obstruct a T's ability to follow the orders. Subject to admin discretion. I'm going to take this situation specifically to explain how this rule can apply. So on summer, if a CT immediately rushes to the cell button and begins to spam the "Close" button while the order given requires the Ts to take a step out of their cells, that CT would absolutely be obstructing their ability to follow that order. That's unreasonable and stupid and there's obviously no justifiable reason to do that. However, this doesn't mean you can hide inside your cell for 1 minute and then come out and complain once you see your cell door is closed. That is completely on you and counts as delaying. This is obviously not really a cut and dry type thing, hence the "subject to admin discretion" part. Admins - just be reasonable when you're handling people like this. It's probably quite easy to see what someone's intentions are when they're continuously closing cells, so just act accordingly. @Caution is completely right in saying there is a completely legitimate reason to close cells after the Ts are out. It is an actual strategy and we don't want to disallow it, we just want to flesh out those people that are actually trolling. I hope this fixes the problem you've addressed in this thread. This will be put in a JB Changelog that will follow this as well as added into the official rule thread. If anyone wants to give feedback on this change, please feel free to do so.

Closed pending amendment.

Or maybe try talking it out with Gentoo before resorting to an admin complaint, that would probably be a better course of action.

The general consensus among the Jailbreak staff is that there's no real way to fix this. That's how it has always been. Yeah, it sucks, but there's no other rule or plugin that could be put in place that would be more effective. We understand where you're coming from and we appreciate the fact that you brought it up, but that's unfortunately how it'll have to stay.

In case anyone was looking for an "official answer", look to Takuto and Fuze's posts.

We've decided that we're not going to move it from where it's at right now. We can take another look in the future because obviously nothing is set in stone but there's no strong argument here for going back to 110 or going down to 100. As always though, we appreciate the feedback.

The credits are now back to normal. It ran for about a week longer than planned, but I'm sure none of you are complaining about having gained some extra credits. Thanks for your continued dedication to the server everyone.

are you implying that you're gonna say yes?

First Order is once again disabled. I'm not going to give anyone false hope - we don't know whether or not we're going to add it back at all yet. This is simply due to the huge amount of problems it's giving us and time it's taking away from us dealing with them.

you guys are really gonna regret this once i hit puberty

Reminder - please join this if you haven't already.

Extremely well deserved, you've put yourself through hell multiple times just for Jailbreak alone in the past two weeks. Can't thank you enough for everything you've done for me and the community as a whole. Congratulations.

No need for another rule. It already counts as a freekill if someone turns on the death-game and you die when you hadn't volunteered. The rule could keep you out of the death-game entirely, but there's spots on maps that serve both as a death-game and a regular activity and I wouldn't want to bar the CTs from utilizing them.

From this thread.

While the idea is awesome, it requires a whole new plugin to be made for a seemingly small benefit. It's not something we want to allocate any time towards currently with all of the projects we have in the works. Thanks for the suggestion though.

Commands implemented - !sm @ts // !su @ts

Going to clarify a couple points real quick: If anyone has any intention of taking this buff beyond 110 HP, it isn't happening. I will never support a buff to that scale because it will then begin to hinder the Ts ability to knife the CTs, which should not change. The buff is in place to help. Does 5 HP help a lot? Maybe, maybe not, but it's literally undeniable that it does help even in the slightest. There were countless times I was left with 1 HP after the 110 HP buff, so in many cases it will save your life. Most of the time, Ts are using glocks or USPs and 5 HP can make a huge difference in those scenarios. Now with that off the table, I'll tell you why I personally felt the change from 110 to 105 was necessary. People won't always approve of changes we make. As a manager of anything, you should know that some people will be happy while others may not. It is almost impossible to come to a compromise that everyone will enjoy. There will always be people who hate on any change for no reason or like every change without reason. However, at the end of the day, our goal is to make the server enjoyable for the players. That is the endgame, to make sure everyone is having a good time. We didn't make the change because we were frightened by all the negative feedback. I took my stance against all of the feedback because there was no real substance behind what anyone was saying and I did and still do feel like the logic behind it is good. However, if there's still a strong dislike for a change after we've let it settle in, we're not going to keep it. It's become a routine to hear "fuck man, 109" or something of the sort when I'm on the server. Will people complain about anything they can? Probably, but this isn't something that we necessarily needed to keep in place. There's no reason to keep it in place and make people rage quit when they hit an AWP shot for 109 when we don't actually need to keep it there. I think it was perfect to balance out those overpowered secrets with AWPs, but we'll just have to take a different route with helping the CTs. Honestly, chances are, we'll probably end up changing how some secrets work like the Razor AWP window. The game is completely unbalanced, if everyone wants to complain about this change, we'll have to do another. Bit repetitive, but my point is that our overall goal is to please the people and if they aren't pleased even after adapting to the change, it's not worth keeping. I'm not telling you guys it's staying at 105, literally everything on the server is subject to change. But for now that's what we as managers see fit and we're going to let it settle in.

You can KOS off of assists.

This has been implemented.