Vertex

Alright, I've talked with Gringo and he was agreed to give you one final chance. The length of your ban has been reduced to six months from the starting date. See here: Xeno Gamers If you prove that you're serious and become a donor I will set your ban to expire this Friday March.25th at 4:22pm server time. (one week from the start date) This is a one time offer which will not be extended again in-order for a reduced sentence. The donation needs to be five dollars as mentioned above and be attached to your forum account. (not anonymous) I will be checking the listing here as proof of donation. https://xenogamers.com/donations/list This is not be any means a bribe because if you start RDMing, spraying pornography or breaking any further rules the ban will go right back on. This donation is non-refundable and does not grant immunity against further rule breaking.

As you can clearly see, Mescapium, you're running of opportunities to start following the server rules and play the game properly. A recommendation has been received to keep your server ban permanent and never remove it. With that being said, I would like to know why YOU think a final chance is justified. And what steps YOU"RE going to take to ensure no more rules are broken, should a final chance be granted. Please ensure your response is meaningful because if i'm not satisfied with it, Gringo's highly respected recommendation will be granted.

You were banned by @CharDraesia for two days. I have asked him comment on this ban. Server Ban Link: Xeno Gamers ~Vertex~ -Morbus Server Operator

This guy has quite a negative history on our Morbus server and forums. The rule breaking just doesn't stop. See previous bans here: Xeno Gamers The first ban protest on our forums happened Jan. 2nd, 2015. He straight up lied about RDMing and didn't take responsibility for it. The thread was immediately closed. H4kzthewaxshieet - garrys mod The second ban protest happened on Jan. 28th, 2015. It regarding his permanent ban for RDMing eight people in a single round. I was nice enough to reduce the ban length to one year. H4kzthewaxshieet - garrys mod Now he's back protesting after anther permanent ban... for spraying pornography, double/triple RDMing then leaving the server. I will let @DoctorGringo weight in his opinion about the best course of action here. IMHO, it may be best set the ban to expire September 18th, 2016 at 4:22pm server time. Progress appears to be getting made here; but, it's still moving far too slowly for our liking.

We need 's u i c i d e' abuse prevention as well. People are regularly using the kill command in console, which, has a lot of negative impacts the gamemode isn't designed to the handle, like imbalances in brood selection.

GPU recommended power specs are always higher than required. They consume a set amount of power much like other components do. A 450 watt power supply can handle the gtx 970 with your typical Intel processor. The NVIDIA GeForce GTX 970 Review: Featuring EVGA

Two things need to happen before TTT is launched. These are the only hold backs, the server has been ready for months. A division manager responsible for handling moderators, ban protests, server rules, population etc. Anther clan hosting needs launched. The current clan hosting(s) cannot safely handle TTT as the load is too high.

I'd rather not punish people for using game flaws. It's better to find a solution to fix issues like these. It would be a good idea to send warnings though and not back them up with anything. That would scare people off without actually punishing them. Edit: I just a found anther implementable solution. Giving swarms spawn protection for three seconds.

You won't be able to fix Teslars yourself, the issue is far too complicated. As for the spawn camping rule, it would do more harm than good. More punishment would be required to handle that issue. If people are camping, mission times should be tweaked to force more walking around the map. But on large maps such as spaceship, humans do not walk fast enough to get around the map for increased missions. Anther way to solve that issue would be to implement attrition on humans in the swarm spawn; but, Demonkush or Resmcar would have to do that.

@DoctorGringo The garry's mod game update did in-fact break things with the morbus gamemode. I just fixed the following issues. Fixed an issue where text boxes render in the wrong place if the client changes screen resolution mid-game Fixed an issue where text was rendering outside the boxes in the top right corner There's a high chance it will break again in the future, let me know if it does I applied a temporary fix by hard-coding the proper location for the text. These issues will get fixed at a later time. Role hints and swarm shot not accounting for changing screen resolution mid-game. Improper text aligment in the swarm shop Improper text aligment on role hints

Easier said than done. In a world where time is never an issue and features never have any bugs when first created, that would be a pretty realistic feature. But it in-reality, there would always be a false ban (more until polished) no matter how rare; and, it would take a lot of time to make that feature. This has been considered; but, if implemented, it certainly won't happen in the near future. A moderator will always be required to handle the small stuff regardless of what has been coded. Automatic voice recognition to see if players are getting harassed for instance certainly isn't a realistic 21st century feature. But it would be nice to mitigate damage caused by mass RDMers.

I also found this concern in the game-server's event log. Do you know if this issue started on the "required" or "optional" update? If it happened on the optional, I can request the provider revert the optional update. Edit: I looked at the changelog, it's very unlikely but still possible that the optional caused this issue. Subject and date Description Subject and date Description

Did this start happening recently? I think it could be a result of the recent gmod game update. If this is the case, I could look over the code but can't promise what i'd be able to accomplish or resolve. How can I reproduce this issue on my game client? Is it as simple as joining and leaving mid-match like you said?

The silence is not getting reduced any further, as ruining game for everyone on the server is not acceptable. You should be appreciative that your ban got removed and the silence was reduced to expire. I could have just kept a permanent ban, since you did ruin a match for everyone. Not being able to communicate is something you'll have to live with, as the only other alternative is being banned from accessing the server entirely. There's nothing more to discuss here, so i'm going to go ahead and close this thread.

Google Translator: I have reduced the duration on the silence to six months as this is much more reasonable. You already had your sever ban removed, the silence will not be reduced any further. Link: Xeno Gamers My top priority is that games do not get ruined by others on the server. This is not a punishment, it's a preventive measure. You still have access to the server, just in a restricted manor to prevent games from getting ruined.

You have a silence instead of a server ban. Silences are used to prevent players from commanding without banning them from the server. It is a multi-purpose feature which also blocks chat & radio messages. As stated in this thread, you were blocked from commanding for ruining the game for everyone on the server. The server rules are on the motd when you first connect to the server. > Redstone Code of Conduct i) Everyone has the right not to be harassed or discriminated against. ii) Players shall not ruin games, spam/advertise, bomb or use hacks/exploits. iii) Avoid the usage of advertisements, to intimidate or deceive people. iv) Commanders shall not violate section i-iii), use build exploits, sell all the spawns or intentionally ruin/throw a populated game. v) Frequently stacking on one faction is not acceptable. It strains the quality of games for everyone on the server in pursuit of personal gain.

That requires testing. It broke when the reload exploit was patched. I'm busy until the weekend. The test server has static spawns on spaceship which I hard-coded into the arming file for testing purposes. That's how it worked when we tested it last, but when it got onto the main server with dynamic spawns (they spawn randomly). It didn't function properly. If you want to test it yourself, you can try putting this file on the test server. Then seeing if spawns work properly (not on spaceship) and the reload exploit is fixed. The directory structure is the same for the test server as posted on github from gamemodes on. Morbus/shared.lua at master · Remscar/Morbus · GitHub

I was thinking remscar's nerf was better as well, should I apply it?

@eyesofdeath983 The uzi is overpowered currently, and needs delt with. The remscar github nerf is an option, or reducing the damage from 13 to 11 is anther option. Right now it's comparable to the m418 assault rifle. uzi remscar github uzi nerf. m418

@eyesofdeath983 Reduce endurance points from 6 to 4 and keep the current 15 health scheme. 6 pretty much invincible with 30% resistance. Before 190 health + 30% resistance After 160 health + 30% resistance

This thread is reserved for balance change proposals.

Uniform will work too. moderator discretion warn if appropriate; otherwise, just ban the client.

@eyesofdeath983 I'd have to do something like this. !Mass Gringo. !Claim Gringo !Porn Gringo It would automatically ban them and notify everyone on the server. This would be easier for moderators as the hard-defined duration would be used instead of having to input a custom duration.

@eyesofdeath983 I think claiming a room could be phrased better. "If it's a kid who doesn't know how to play, warn then ban on repetition; otherwise, ban for two weeks."

I think certain major offensives that everyone agrees with can be broadcasted; but, as far as sending everything, this will do more harm than good. For instance these things should be broadcasted. > Gringo was removed from the server for spraying pornography. Gringo was removed from the server for mass rdming. (shooting everyone on sight) Gringo was removed from the server for claiming a room. (shooting everyone who entered it) Controversial things shouldn't broadcasted. > Gringo was slayed for rdming someone. Gringo was banned because he keeps rdming.