Merge remote-tracking branch 'origin/master' into Delta-RnD-Med

.github/ISSUE_TEMPLATE/issue_report.yml

@@ -10,9 +10,9 @@
 #    label:       | Box title |
 #    description: | Box small text - Description |
 #
-name: "Issue Report"
+name: 'Issue Report'
 #title: "[Bug]: " | if you want to have a have it automatically say [Bug] when they start the form
-description: "Доложите о проблемах или багах, что бы мы могли их исправить."
+description: 'Доложите о проблемах или багах, что бы мы могли их исправить.'
 #labels: "Баг"
 
 body:
@@ -24,7 +24,9 @@ body:
     id: version
     attributes:
       label: BYOND Version
-      description: "На какой версии BYOND встретился баг. (Если уверены, что не связано, можно пропустить)"
+      description: 'На какой версии BYOND встретился баг. (Если уверены, что не связано, можно пропустить)'
+    validations:
+      required: true
 
   - type: textarea
     id: description

.vscode/settings.json

@@ -8,7 +8,8 @@
 	"typescript.enablePromptUseWorkspaceTsdk": true,
 	"search.exclude": {
 		"**/.yarn": true,
-		"**/.pnp.*": true
+		"**/.pnp.*": true,
+		"tgui/public/**/*": true
 	},
 	"eslint.format.enable": true,
 	"eslint.rules.customizations": [

CODE_OF_CONDUCT.md

@@ -42,10 +42,14 @@ It is expected that contributors discuss larger changes on the [Paradise Station
 
 For changes to content listed below, contributors **must** obtain approval from a headcoder or a member of either the balance, design, mapping, or sprite team (depending on which teams are relevant to the changes) before opening their Pull Request. This approval must be displayed in the Pull Request description body in the form of a screenshot. The Headcoders may grant an exemption to this requirement on a case-by-case basis, as the need arises.
 
-### Currently, changes to the following types of content requires pre-approval:
-  - Security content (excluding fixes, code improvement, refactors, sprites, and mapping changes)
-  - Antagonist content (excluding fixes, code improvement, refactors, sprites, and mapping changes)
-  - Species content (excluding fixes, code improvement, and refactors)
-  - Large changes (for example PRs that touch multiple systems, many files, many lines of code)
-  - Changes that might be controversial
-  - Changes with wide-ranging balance or design implications
+<!-- Add a fixed link so that changing the heading name doesn't break the link. -->
+<a id="types-of-changes-that-need-approval"></a>
+
+> [!IMPORTANT]
+> ### Currently, changes to the following types of content requires pre-approval:
+>  - **Security content (excluding fixes, code improvement, refactors, sprites, and mapping changes)**
+>  - **Antagonist content (excluding fixes, code improvement, refactors, sprites, and mapping changes)**
+>  - **Species content (excluding fixes, code improvement, and refactors)**
+>  - **Large changes (for example PRs that touch multiple systems, many files, many lines of code)**
+>  - **Changes that might be controversial**
+>  - **Changes with wide-ranging balance or design implications**

SQL/paradise_schema.sql

@@ -711,3 +711,31 @@ CREATE TABLE `budget` (
 # Adds species whitelist ~legendaxe
 
 ALTER TABLE `player` ADD `species_whitelist` LONGTEXT COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT ('["human"]');
+
+# Updating DB from 59.220.6 to 59.220.7
+# Adds SS220 toggle prefs ~Maxiemar
+
+DROP TABLE IF EXISTS `player_220`;
+CREATE TABLE `player_220` (
+	`ckey` VARCHAR(32) NOT NULL COLLATE utf8mb4_unicode_ci,
+	`toggles` int(11) DEFAULT NULL,
+	PRIMARY KEY (`ckey`) USING BTREE
+) COLLATE = utf8mb4_unicode_ci ENGINE = InnoDB;
+
+ALTER TABLE `player_220`
+ADD CONSTRAINT `fk_player_220_ckey`
+FOREIGN KEY (`ckey`) REFERENCES `player`(`ckey`)
+ON DELETE CASCADE
+ON UPDATE CASCADE;
+
+DROP TRIGGER IF EXISTS `player_insert`;
+DELIMITER //
+CREATE TRIGGER `player_insert`
+AFTER INSERT ON `player`
+FOR EACH ROW
+BEGIN
+    INSERT INTO `player_220` (`ckey`)
+    VALUES (NEW.ckey);
+END;
+//
+DELIMITER ;

SQL/updates220/59.220.6-59.220.7.sql

@@ -0,0 +1,31 @@
+# Updating DB from 59.220.6 to 59.220.7
+# Adds SS220 toggle prefs ~Maxiemar
+
+DROP TABLE IF EXISTS `player_220`;
+CREATE TABLE `player_220` (
+	`ckey` VARCHAR(32) NOT NULL COLLATE utf8mb4_unicode_ci,
+	`toggles` int(11) DEFAULT NULL,
+	PRIMARY KEY (`ckey`) USING BTREE
+) COLLATE = utf8mb4_unicode_ci ENGINE = InnoDB;
+
+ALTER TABLE `player_220`
+ADD CONSTRAINT `fk_player_220_ckey`
+FOREIGN KEY (`ckey`) REFERENCES `player`(`ckey`)
+ON DELETE CASCADE
+ON UPDATE CASCADE;
+
+DROP TRIGGER IF EXISTS `player_insert`;
+DELIMITER //
+CREATE TRIGGER `player_insert`
+AFTER INSERT ON `player`
+FOR EACH ROW
+BEGIN
+    INSERT INTO `player_220` (`ckey`)
+    VALUES (NEW.ckey);
+END;
+//
+DELIMITER ;
+
+INSERT INTO `player_220` (`ckey`)
+SELECT `ckey`
+FROM `player`;