All Activity

November 17th Changelog Overhauled the custom class creator menu so it's more modern and user friendly You can now customize your custom class join command from within the class creator / editor Overhauled the boombox to support Spotify. Cached youtube videos should still work Squashed over 75 serverside lua errors to improve server stability Fixed the blackjack table canceling the game and stealing your money if the round resulted in a push Made it so being votekicked/banned will automatically export your client logs Fixed a rare issue where destroying printers may cause staff to disconnect Fixed an issue where effects would not be active if you equipped an enchanted weapon directly from inventory Fixed a bug when filtering jackpot winnings within the claim menu Fixed a bug where revoking a weapon license could fill the entire screen with text Fixed a bug where the mayor might not be fully demoted on unfun Small optimizations to the bird job makes it easier to take off when the server is under heavy load Cereal leaderboard now tracks cereal found instead of cereal spent Increased a player's movement speed slightly from where it was when they're cuffed Fixed a visual bug where using inventory items in "pounds" would not decrease the count when dropped Merged a patch for CH Bitminers that fixes a money exploit Fixed a rare bug where if your opponent disconnected during a gang war it might not mark you as the winner Patched an exploit where malicious players could fill the map with blacklisted effects Fixed newly created CCs not appearing in the F4 menu until relog

October 24th Changelog (Staff) added the option to spectate the reported player from the sit menu Added a toggle to the help menu to disable all dumpster effects for max performance Smooching a player as a spooky alien will preserve any Max HP buffs Made it so you will only be team banned if demoted from a Police job Blood sucker talent will preserve any Max HP buffs Gersh device HUD and QOL improvements Fixed a rare lua error when reloading with a deployer (maxwell) swep equipped Deployable entities such as maxwell can no longer be used in spawn Prevent spawning of blacklisted constraints using AdvDupe2 for performance and stability

October 20th Changelog Fixed boombox and theater conversion failures Patched a physics related server crash due to meth lab Fixed a bug where a user might be able to free-cam while shamed Fixed scratch offs not giving quest progress if you hit a jackpot

October 15th Changelog Updated Thief/Raiding Rules Rearranged Raiding Rules Add: Raid District rules from forums to rules page with some modifications to the writing: During a raid you may go anywhere in the district to defend your raid. However, you may not kill anyone in the district that isn't involved in the raid. Raid counters/takeovers are not allowed so someone just existing in the district should not be default KOS to you unless they are on the doors or interfering with the raid in some way. Once you leave the district you end the raid/raid defence. If you die while defending the base you may not return to the base until the raid is over. Returning to the other side of the district is fine if you are not spectating or interfering with the raid. When raiding any base in sewers, when you enter the ring that surrounds the sewers this counts as leaving the district. Use common sense when raiding for how far is too far from the base when raiding. Only exception is when chasing down an external defender. Kingdom is its own district, leaving Kingdom during a raid will end the raid. Raid District rules do not apply for PD and Bank Raids. Same rules just rewritten to clarify it further to remove confusion and grey areas. New additions listed below. Add: Raid counters/takeovers are not allowed. Exception for PD, Bank and Kingdom raids. Add: If you die while defending the base you may not return to the base until the raid is over. Returning to the other side of the district is fine if you are not spectating or interfering with the raid. Add: Kingdom is its own district, leaving Kingdom during a raid will end the raid. Note: These 2 rules were changed from what they were so to encourage better roleplay, Events such as PD and Bank raid should be countered so it's higher stakes to loot inside or to overthrow the current power. The returning to the district is so that people who may die during a raid are not locked off from an entire section of that map for at most 10 minutes. Returning to spectate a raid is still not allowed. Updated Citizen Rules Removed: You may counter bank heists if you are: a cop, bank guard, bank manager, or are inside the bank with the raid begins Removed: You may not counter PD Raids if you are not a cop or are in the PD when the Raid begins

October 14th Changelog Patched an exploit that allowed a user to crash the server Readded Halloween map and BP tiers Added the option to disable all inventory effects and rounded boxes for maximum FPS Added a HUD to the bank drill that shows you if it is on cooldown or not Added an icon to the HUD that shows if precious life is active for you Added a timer to the inventory if there is a cooldown on using the item Chat tags will now show their rarity like pets do from the inventory Made it so staff cannot accidentally move the kingdom area walls Fixed a bug where there could be two mayors simultaneously Fixed a bug where the leaderboards would reset too soon Fixed a bug where you would be unable to use the printer screen Fixed a bug where the talisman hud might not draw in the right position

October 6th Changelog Added a new "Dead Meme" companion lootbox to the Suga Shop. It contains 2 common, 2 rare, 1 epic, and 1 legendary You can now select individual items to keep when claiming your coinflip winnings in case you don't want everything You can now see who's behind you in the leaderboards. This is to help combat leaderboard sniping Leaderboards will now reset at the same time every week (Sunday at 8am Eastern) Stalking a player as Master Stalker will now show a "Sanity" bar which correlates to the severity of the effect on them Faded props will attempt to check if a player is colliding with it before unfading. This helps players from getting stuck Added a no-build zone to the casino to prevent players from blocking off slot machines and tables Capped the number of NPCs you can spawn at any time to 5. This is to prevent players from causing FPS drops Fixed a bug where you would not be able to spend your lootbox tokens if you had more than 63 tokens Fixed sorting the scoreboard by playtime where it would only take into account the first number Fixed a bug where you may be able to see an extra Goon Egg without unlocking the talent Added a HUD element that shows you how much premium gas you have left Disabled the precache model limit since the engine handles this now Fixed a bug that may cause your screen to blur until relog Patched a bug that allowed you to revive a downed cop while dead Fixed bounty hunter being unable to complete a job Fixed a typo in the CC creator menu

September 15th Major Changelog [Halloween 2024 Update] Added the Halloween map with backrooms Added Halloween 2024 battlepass Added 2 new pets to the Halloween pet lootbox for 2024 Added new emotes for 2024; unlockable through the battlepass Zombie apocalypse world event Free Halloween-themed playermodels to the CC editor and !ms Pumpkins that spawn around the map that can be squished for XP Halloween-themed loading screen and forums Fixed the settings menu switches not saving on relog Added an optional context menu popup for your current battlepass task (disabled in help menu by default) Clicking retry from the crash menu will try to reconnect you Fixed rare lua error with the zombie bunny pet Fixed crouch-walk animations for pets if it has one

September 6th Changelog Boomboxes will show as "free" on the entities tab if you have unlocked that in the Suga Shop The auction house will always recommend a price if market history is available and it's greater than the default price Fixed a rare lua error when trying to sell an enchanted weapon on the marketplace that did not have any market history Fixed not being able to spawn more than 3 buttons with the advdupe2 tool when the limit is 5 Fixed an issue where bounty targets may not reset after a player turns themselves in Fixed an issue where the boombox may break some UI elements, such as sub-text inside the lightning quest popup Reversed a change to mini printers due to an increase in physics-related server crashes. Will continue to monitor for improvements Fixed a bug where you might be able to cancel a coinflip after an opponent was already registered Reversed a recent change that may prevent the Legacy Job Picker menu from opening [fb816f4] Fixed the CSS Glock view model and missing hands Fixed an issue where if you called a sit for RDA it would classify it as "AOS" instead Patched an item duplication exploit [bb8a762] Patched a minor exploit [ea1502b]

Administrator Training Guide Welcome to the Admin team! First, let's start off with a quick refresher of the Moderator / Admin Guidelines and the Admin Overview and Responsibilities. You must know and understand everything in those threads because we will avoid covering those topics here and focus mainly on your transition from Senior Moderator to Administrator. Note: this thread will be updated regularly so check back often for the latest info. Removing Rep How: Click View Rep on a player from the scoreboard, then right-click on the rep that you want to remove, then select Remove Rep. Remove rep for a player only at their request or when the rep message contains any content that violated the server rules. This includes racist, harmful, or offensive language. Do not remove Rep just because the person doesn't like it. When a player requests that a rep be removed, you must remove all instances of false/offensive rep. This includes positive ones. Inform the player that this may negatively affect their overall rep. If they want to proceed, go through their entire rep history and remove anything that violates the server rules. Note: It may take some time before these changes reflect the user's dashboard profile. Removing Bans How: Open the staff menu with !menu, click Bans, then type in the user's SteamID. Right click the ban, then select Delete Ban. This will unban the user and remove it from their record completely. Removing bans only works on active bans. There is currently no way to delete existing or expired bans from a user's record. For that you will need to reach out to a Superadmin for help because it needs to be manually deleted from the database. Remember this is not the same as unbanning because when you unban a user, it will still remain on their record. Note: It may take some time before these changes reflect the user's dashboard profile. Accepting S-Mod Applications As you know by now, the Senior Moderator application process is very different than the regular T-Mod application process. It will take significantly more time before you should accept an S-Mod application due to the nature of how it's setup. Part of the application process is testing the applicant's patience and motive. Are they applying just for the rank? Will they remain active even if they aren't accepted right away? Because of this, you should wait at least 7 days and for the application to gain a majority of positive feedback before accepting it. After accepting the application, you need to do the following: Reach out directly to the applicant via Discord to inform them that their application was accepted (they can't see the accepted applications forum so this is important) Reach out to the applicant on Discord a second time and schedule a time/date that they are available to be trained Set their rank to Senior Moderator in-game (Discord and forums roles will be automatically applied after some time) Train them in game, covering all of the topics listed in Senior Moderator Overview and Responsibilities Locate their thread in #tmod-upkeep, right click it, and choose Edit Tags. Add the Senior Moderator tag Create a new post in #staff-info containing the following format: SMod Name: <applicant name> SteamID: <applicant steamID> Trained By: <whoever trained them> Watched Over By: <your name if applicable> On occasion, an S-Mod may ask you if they can conduct the training. This is completely fine as long as you are actively monitoring the training and provide support if needed. This is a great way for S-Mods who have their sights set on Admin to gain some valuable experience for the future. You are fully responsible for the quality of the training that they do so do be heavily involved in the process. Perma-Bans / Community Removals As an Admin, you may ban a user indefinitely in accordance with the server rules and our terms of use. Remember, the max ban for most situations is 6mo. It is your responsibility when extending bans to verify that a community removal is an appropriate punishment and within the punishment guidelines. Once you extend it to permanent, it becomes your responsibility since no one besides you and Superadmins have the authority to reverse it. Community Removals require a thorough and well-informed group decision so never rush to conclusions. It's best practice to make a post in either #decision-making or #admin-chat for sensitive topics. Rule Changes How: Go to https://titsrp.com/adminrules and login. Make the approved changes and then click save. Log your changes. On the rare occasion that something in the server rules needs to be updated or removed, you may make those changes after majority approval from the rest of the Admin team and the Superadmin. It's best practice to post the proposed changes in #decision-making and include the rest of the staff team as well. If it's a good rule change, there's no reason to not include everyone. All changes to the server rules must be logged to the forums. Failure to do so will jeopardize the integrity of the server rules and you risk being demoted. Server Reboots In situations where the server is frozen / stops responding, it is designed to reboot itself after no more than 5 minutes. Always wait at least 20 minutes after the initial report before taking any action. Never reboot the server before you have exhausted all other options to fix the issue Never reboot the server before you have tried to contact Rubik several times via pings in #admin-chat, DMs, or other methods and **at least 20 minutes has passed** Never reboot the server multiple times to try and fix an issue. If it isn't fixed the first time, a reboot will not solve the issue Never turn off / stop the server unless you have tried a reboot with no success DO reboot the server if: The entire server reports that their inventory is missing **Literally no one** is able to connect, including yourself and other admins The server has been offline or down for more than 20 minutes and there is no communication from Rubik in #announcements The server has failed to reboot itself after a crash or scheduled reboot *(will show as "Stopped" in the panel)* DO NOT reboot the server if: A small number of players say they are unable to connect Someone says they are missing item(s) from their inventory Someone is lagging or DDoSing the server Someone is exploiting / duping *(ban the person(s) instead)* You have already rebooted the server once and the issue still persists