Benjamin Krueger blueben

Something is down! What should we do?

First: Breathe. It’s just tech. We’ll fix it.

Slow down. Hasty decisions won’t help us be operational again. In fact, they often lead to making more mistakes. Remember to "Go slow to go fast". We have time to think before we act.

The formal process described here helps us slow down and think. When possible an oncall engineer should be paired with a more senior or experienced mentor engineer, and the oncall engineer should try to execute as much of this process themselves. The oncall/mentor pairing primarily intends for mentors to support fellow engineers in their oncall and engineering journey, providing a backstop only when necessary.

The Incident Management Process

	# table: svs_events

	event_id: uniq
	event_name: "name"
	event_start: UTC datetime
	event_end: UTC datetime

	# table: event_teams

	team_id: uniq

	Hi! I don't work for VRC, I'm just a player. But I do want to address some of the issues relating to the elimination of VRChat client mods brought up in the VRChat feedback system. This is a direct response to this post: https://feedback.vrchat.com/open-beta/p/eac-in-a-social-vr-game-creates-more-problems-than-it-solves

	Firstly, I think it's important that people know that you (knah) maintain a large repository of VRC mods. I don't think anyone would consider them malicious, but it is important for folks to be aware of your bias in this matter. Anti-cheat will make a lot of the work you've done obsolete and that has to be a hard pill to swallow.

	================================
	* Most games that use EAC (or other anti-cheats) still have cheaters. For VRChat, this means that malicious mods will still exist and be used to annoy people in publics.
	================================

	This is technically correct. It is also irrelevant. Of course there will always be cheaters. The goal isn't to make cheating imposs