New gamepad types, button labels, conventional/default "confirm"/"cancel" buttons by nstbayless · Pull Request #15891 · libsdl-org/SDL

nstbayless · 2026-06-26T21:02:32Z

I confirm that I am the author of this code and release it to the SDL project under the Zlib license. This contribution does not contain code from other sources, including code generated by a Large Language Model ("AI").

Description

It's a long-standing problem that games don't properly respect "confirm" and "cancel" buttons on some gamepad types (they'll either assume xbox convention of EAST=cancel, SOUTH=confirm; or, more rarely -- but I've seen this on some recent steam demos for example -- nintendo convention of EAST=confirm and SOUTH=cancel). Additionally, games have to roll their own detection of gamepad type to determine what kind of glyphs to show.

This is particularly bothersome when using, for example, a SNES controller with a usb adaptor, or other retro gamepads with USB adaptors. It's not common for games to detect these more rare kinds of gamepads. Sega layout in particular tends to confuse games.

I'd like to make progress toward the eventual goal of having SDL be able to identify exactly what glyphs should be shown (even if SDL doesn't itself ship with the actual glyphs), and make it easier for game devs to identify and handle different gamepad types more broadly.

New Gamepad Types

I've added a handful of gamepad type enums that I think are famous and interesting enough to warrant supporting their glyphs, and not similar enough to any existing gamepad to be able to be rolled into e.g. the standard or xbox 360 layout. This includes: ~~NES~~, SNES, N64, ~~SEGA Master System~~, SEGA Genesis, ~~SEGA Saturn, TurboGrafx-16, Neo Geo, and 3DO~~.

I've also clarified the comments here a bit to reflect what I've found in the code and the standard practices in SDL GamepadControllerDB.

New Gamepad Button Labels

There was already some work in this direction in SDL, but it was incomplete. I've fleshed it out now, adding all the most common button labels I've encountered, including all button labels used by the gamepad types above. I've also added labels for numbers 1-9 even though only some of those are actually used by supported controllers right now, under the expectation that they'll eventually gain support in the future. (For example, atari/jaguar models with keypads 1-9? Or arcade gamepads?)

"Conventional Actions"

For common UI actions that are platform-dependent. For now, I've just added "confirm" and "cancel" (since these are generally either SOUTH/EAST or EAST/SOUTH, though on gamecube it's SOUTH/WEST) but I could see onscreen keyboard controls being added to this too. For PS4 (and PS3?) it's region-dependent, so users in japan with a PS4 controller will get the expected CIRCLE=confirm, CROSS=cancel.

DB Changes

Removed "face:" field in db; it seems like this basically wasn't used anyway and it's less info than is in the new "type:" field.
Added "type:" field, a more general system to replace the rather deficient "USE_BUTTON_LABELS" scheme. (example: type:n64, type:switchpro, type:gamecube, type:ps5, etc.)

Lingering Issues

Axes don't get labels yet. There's no way to know, for example, that what SDL calls "left trigger" is actually the sega genesis "R" button. (It seems weird to me, but that's actually the standard for some reason!)
db can now be updated with tags like type:snes and so on. This was suggested in an issue for the DB before, but it was suggested to be pushed upstream to SDL first I think?
Since SDL3 is moving away from "a/b/x/y" notation in favour of the more general "south/east/west/north" notation, it'd be nice to let the gamepad db use that notation too instead, e.g. "south:b0".
What is a SDL_GAMEPAD_TYPE_STEAM? Is it any controller under steam input, or only steam controller? steam deck? SC1 and SC2 have different button labels... Not sure what to do here!
SDL_GetGamepadButtonFromString seems broken to me... it turns a button string into its enum equivalent, but for some reason also takes into account abxy/axby arrangement? and doesn't handle playstation button names? I'm not sure what it's even trying to achieve here. I think this is all caused by not using compass notation and somebody got confused.
I omitted labels for the center/guide button. I don't really know what the fallback should be (I would not personally recognize "guide" button, and "center" is ambiguous on some gamepads; "system" or "meta" are what I'd lean toward personally), and I don't know what it should be called on the common gamepads.

icculus · 2026-06-27T03:55:02Z

I don't know that we need all the different controller layouts (but I'm not necessarily against it), but I do like the confirm/cancel idea.

nstbayless · 2026-06-27T06:01:36Z

Okay, I can roll SNES/NES into one gamepad type; Saturn/Genesis into one gamepad type; and postpone Master System/TurboGrafx-16/Neo Geo/3DO to a later PR if we're not sure about those yet (they're definitely less common). But at least SNES, Sega, and N64 are important to codify IMO, they're very common, and Sega layout even has documentation on the db readme, and relevant to the confirm/cancel convention.

icculus · 2026-06-27T18:47:19Z

Let's hold off until @slouken chimes in.

I don't think having this list is useless, because (for example) a Genesis controller doesn't map well to modern gamepads and that's worth knowing if you hit this situation, but I also wonder if games will be interested in offering that level of customization when the gamepad API is meant to avoid those details. Also, I worry about the slippery slope of the whole thing. But that's not me saying it's a bad idea!

But no matter what else, I definitely want the confirm/cancel functionality. This has come up for me multiple times on shipping console titles.

cgutman · 2026-06-27T22:26:40Z

We could also add SDL_GamepadConventionalAction values for primary/secondary menu buttons. For example, games typically use SDL_GAMEPAD_BUTTON_TOUCHPAD for accessing in-game inventory, map, etc. on PS4/PS5 controllers, while they use SDL_GAMEPAD_BUTTON_BACK for the inventory/map on Xbox.

slouken · 2026-06-27T23:59:49Z

+static bool SDL_GamepadLocaleIsJP(void)
+{
+    int count = 0;
+    int i;
+    SDL_Locale **locales = SDL_GetPreferredLocales(&count);

-        face_style = gamepad->face_style;
+    // check if first locale which specifies a country is jp
+    if (locales) {
+        for (i = 0; i < count; ++i)
+        {
+            if (locales[i]->country)
+            {
+                if (SDL_strcasecmp(locales[i]->country, "jp") == 0)
+                {
+                    SDL_free(locales);
+                    return true;
+                }
+                else
+                {
+                    SDL_free(locales);
+                    return false;
+                }
+            }
+        }
+        SDL_free(locales);
    }
-    SDL_UnlockJoysticks();
+    return false;
+}


Suggested change

static bool SDL_GamepadLocaleIsJP(void)

{

int count = 0;

int i;

SDL_Locale **locales = SDL_GetPreferredLocales(&count);

face_style = gamepad->face_style;

// check if first locale which specifies a country is jp

if (locales) {

for (i = 0; i < count; ++i)

{

if (locales[i]->country)

{

if (SDL_strcasecmp(locales[i]->country, "jp") == 0)

{

SDL_free(locales);

return true;

}

else

{

SDL_free(locales);

return false;

}

}

}

SDL_free(locales);

}

SDL_UnlockJoysticks();

return false;

}

static bool SDL_GamepadLocaleIsJP(void)

{

bool japanese_locale = false;

SDL_Locale **locales = SDL_GetPreferredLocales(NULL);

// check if first locale which specifies a country is jp

if (locales) {

for (int i = 0; locales[i]; ++i) {

if (locales[i]->country) {

if (SDL_strcasecmp(locales[i]->country, "jp") == 0) {

japanese_locale = true;

}

break;

}

}

SDL_free(locales);

}

return japanese_locale;

}

slouken · 2026-06-28T00:00:55Z

My first impression is that this is a little much, but let me think on it.

nstbayless · 2026-06-28T22:02:18Z

@cgutman re: touchpad; I'm not so sure... I think on PC, most people with a PS5 gamepad would likely expect the select/share button to act like a typical left-of-center button (and open a secondary menu). This would be my preference at least -- the touchpad thing always seemed to me like a hacky workaround for sony's commandeering of the select button for "share." However, I recognize this is a matter of opinion, and to be consistent with the other principles I laid out, it'd be sensible to have touchpad be the preferred secondary button on PS5. Let's defer it to a later PR at least.

nstbayless · 2026-06-28T22:47:44Z

Since it seems like everyone is saying "this seems like too much," I've reduced the number of additions here. The only new gamepad types now are SNES, N64, and SEGA Genesis. I feel these are essential to add support for; and N64 layout, with B on the west and A on the south, is again an "interesting" case in the confirm/cancel layout.

slouken · 2026-07-04T14:28:34Z

This is looking much better, thanks for trimming it down. I'll add specific feedback below.

slouken · 2026-07-04T14:29:02Z

+ * PSX and PS2 controllers should be classified as PS3.
+ *
+ * Sega Saturn controllers should be classified as Sega Genesis.
+ *


Suggested change

*

slouken · 2026-07-04T14:33:37Z

    SDL_GAMEPAD_BUTTON_LABEL_SQUARE,
-    SDL_GAMEPAD_BUTTON_LABEL_TRIANGLE
+    SDL_GAMEPAD_BUTTON_LABEL_TRIANGLE,
+    SDL_GAMEPAD_BUTTON_LABEL_C,


Adding all the labels for all possible controllers is a monumental task and one that never ends, as controller vendors add new and unique buttons to their controllers. Rather than promising SDL can provide all possible labels, we should have a different system, possibly dynamic, or punt entirely.

For example, this is Microsoft's attempt, and you'll notice that it's even missing a bunch that you've included here:
https://github.com/microsoftconnect/GameInput/blob/6d1f7bfaa3361a7c0d1ba1879c37e02c5828f73a/include/GameInput.h#L367-L493

Just as an example of this, you're missing the L2/L3 buttons, the DualSense Edge has Fn buttons, and the new Steam Controller has a QAM button that's labeled ". . ."

L3 is present in the PR already. L2 omitted in this PR because it's an axis, not a button -- a future PR could address that. Steam Controller I haven't touched because I'm not sure what controller GAMEPAD_TYPE_STEAM refers to (I mentioned this in the PR). PS5 fn button is a fair point.

I only aim to support the labels of the gamepads in the gamepad type enum, which is why I removed some labels when I trimmed down the PR. Since there are a small number of these, the number of labels to add is small.

If we want to support every controller, not just the prototypes which have an enum, then unusual controllers in the database could be annotated with custom labels, perhaps.

I only aim to support the labels of the gamepads in the gamepad type enum, which is why I removed some labels when I trimmed down the PR. Since there are a small number of these, the number of labels to add is small.

That's a good point, and with that scope, what you've done seems very reasonable.

slouken · 2026-07-04T14:40:45Z

+typedef enum SDL_GamepadConventionalAction
+{
+    SDL_GAMEPAD_CONVENTION_CONFIRM, /* typically 'A' */
+    SDL_GAMEPAD_CONVENTION_CANCEL, /* typically 'B' */
+    /* TODO - onscreen keyboard actions */
+} SDL_GamepadConventionalAction;


Suggested change

typedef enum SDL_GamepadConventionalAction

{

SDL_GAMEPAD_CONVENTION_CONFIRM, /* typically 'A' */

SDL_GAMEPAD_CONVENTION_CANCEL, /* typically 'B' */

/* TODO - onscreen keyboard actions */

} SDL_GamepadConventionalAction;

typedef enum SDL_GamepadAction

{

SDL_GAMEPAD_ACTION_CONFIRM, /* typically 'A' */

SDL_GAMEPAD_ACTION_CANCEL, /* typically 'B' */

} SDL_GamepadAction;

slouken · 2026-07-04T14:42:27Z

 extern SDL_DECLSPEC SDL_GamepadButtonLabel SDLCALL SDL_GetGamepadButtonLabel(SDL_Gamepad *gamepad, SDL_GamepadButton button);

+/**
+ * Convert from an SDL_GamepadButtonLabel enum to a string.


I'm not sure this is useful, especially for things like "Triangle" and "Minus" which would need to be localized. Also see my note above about the proliferation of different button labels. What's the use case for this?

Perhaps Triangle/Minus can be replaced with unicode representations of the glyphs -- I can update the PR to do this.

I view these as primarily being useful for e.g. looking up a filename to show the appropriate glyph/button image, but also usable as fallback to display literally if no image is present. The images can be further separated by controller type to exactly match the colour and style as needed, but this at least allows applications to fall back to another glyph with a matching label even if the exact controller type is not recognized (and then to a plain string if the label has no glyph either).

Perhaps Triangle/Minus can be replaced with unicode representations of the glyphs -- I can update the PR to do this.

Minus and Plus can probably be the literal "-" and "+".

slouken · 2026-07-04T14:43:17Z

+ *
+ * \sa SDL_GetGamepadConventionalActionButton
+ */
+extern SDL_DECLSPEC SDL_GamepadButton SDLCALL SDL_GetGamepadConventionalActionButtonForType(SDL_GamepadType type, SDL_GamepadConventionalAction action);


Suggested change

extern SDL_DECLSPEC SDL_GamepadButton SDLCALL SDL_GetGamepadConventionalActionButtonForType(SDL_GamepadType type, SDL_GamepadConventionalAction action);

extern SDL_DECLSPEC SDL_GamepadButton SDLCALL SDL_GetGamepadActionButtonForType(SDL_GamepadType type, SDL_GamepadAction action);

slouken · 2026-07-04T14:43:56Z

+ *
+ * \sa SDL_GetGamepadConventionalActionButtonForType
+ */
+extern SDL_DECLSPEC SDL_GamepadButton SDLCALL SDL_GetGamepadConventionalActionButton(SDL_Gamepad* gamepad, SDL_GamepadConventionalAction action);


Suggested change

extern SDL_DECLSPEC SDL_GamepadButton SDLCALL SDL_GetGamepadConventionalActionButton(SDL_Gamepad* gamepad, SDL_GamepadConventionalAction action);

extern SDL_DECLSPEC SDL_GamepadButton SDLCALL SDL_GetGamepadActionButton(SDL_Gamepad *gamepad, SDL_GamepadAction action);

slouken · 2026-07-04T14:45:32Z

 _SDL_GetGamepadButtonFromString
 _SDL_GetGamepadButtonLabel
 _SDL_GetGamepadButtonLabelForType
+_SDL_GetGamepadButtonLabelString


You can't add functions in the middle of the exports. You should revert all your dynapi changes, rebase against main, and then run gendynapi.py to automatically generate the exports.

slouken · 2026-07-04T14:47:09Z

            SDL_strlcat(mapping_string, "a:b1,b:b0,back:b4,dpdown:h0.4,dpleft:h0.8,dpright:h0.2,dpup:h0.1,leftshoulder:b9,leftstick:b7,lefttrigger:a4,leftx:a0,lefty:a1,rightshoulder:b10,rightstick:b8,righttrigger:a5,rightx:a2,righty:a3,start:b6,x:b3,y:b2,hint:!SDL_GAMECONTROLLER_USE_BUTTON_LABELS:=1,", sizeof(mapping_string));
    } else if (SDL_IsJoystickSInputController(vendor, product)) {

-        Uint8 face_style = (guid.data[15] & 0xE0) >> 5;


You're changing the protocol of shipping controllers. You should check with the author to see if this is okay.

slouken · 2026-07-04T14:47:31Z

+    }
+    else if (SDL_strstr(gamepad->mapping->mapping, "SDL_GAMECONTROLLER_USE_BUTTON_LABELS")) {


Suggested change

}

else if (SDL_strstr(gamepad->mapping->mapping, "SDL_GAMECONTROLLER_USE_BUTTON_LABELS")) {

} else if (SDL_strstr(gamepad->mapping->mapping, "SDL_GAMECONTROLLER_USE_BUTTON_LABELS")) {

slouken · 2026-07-04T14:48:03Z

+        if (gamepad->type != SDL_GAMEPAD_TYPE_NINTENDO_SWITCH_PRO
+            && gamepad->type != SDL_GAMEPAD_TYPE_NINTENDO_SWITCH_JOYCON_LEFT


SDL style leaves the && at the end of the line:

Suggested change

if (gamepad->type != SDL_GAMEPAD_TYPE_NINTENDO_SWITCH_PRO

&& gamepad->type != SDL_GAMEPAD_TYPE_NINTENDO_SWITCH_JOYCON_LEFT

if (gamepad->type != SDL_GAMEPAD_TYPE_NINTENDO_SWITCH_PRO &&

gamepad->type != SDL_GAMEPAD_TYPE_NINTENDO_SWITCH_JOYCON_LEFT

slouken · 2026-07-04T14:48:43Z

+    switch (type)
+    {


Suggested change

switch (type)

{

switch (type) {

SDL style puts braces at the end of the line.

slouken · 2026-07-04T14:49:22Z

+            if (type == SDL_GAMEPAD_TYPE_PS3)
+                return SDL_GAMEPAD_BUTTON_LABEL_SELECT;


SDL style always uses braces for conditionals:

Suggested change

if (type == SDL_GAMEPAD_TYPE_PS3)

return SDL_GAMEPAD_BUTTON_LABEL_SELECT;

if (type == SDL_GAMEPAD_TYPE_PS3) {

return SDL_GAMEPAD_BUTTON_LABEL_SELECT;

}

slouken · 2026-07-04T14:50:52Z

-    SDL_LockJoysticks();
-    {
-        CHECK_GAMEPAD_MAGIC(gamepad, SDL_GAMEPAD_BUTTON_LABEL_UNKNOWN);
+static bool SDL_GamepadLocaleIsJP(void)


Any particular reason you didn't take my suggested edits here? Your code doesn't follow the SDL style and has the unnecessary count variable.

Sorry -- the github interface for some reason 500-errored when I tried to accept your edits, and I wasn't sure how to copy the code without getting a + at the start of the line. So I just made the edits myself, seemed faster. My apologies, I should have paid closer attention.

slouken · 2026-07-04T14:52:01Z

    "050000006964726f69643a636f6e0000,idroid:con,a:b1,b:b2,back:b8,dpdown:h0.4,dpleft:h0.8,dpright:h0.2,dpup:h0.1,leftshoulder:b4,leftstick:b10,lefttrigger:b6,leftx:a0,lefty:a1,rightshoulder:b5,rightstick:b11,righttrigger:b7,rightx:a2,righty:a3,start:b9,x:b0,y:b3,",
    "03000000b50700001503000010010000,impact,a:b2,b:b3,back:b8,dpdown:h0.4,dpleft:h0.8,dpright:h0.2,dpup:h0.1,leftshoulder:b4,leftstick:b10,lefttrigger:b5,leftx:a0,lefty:a1,rightshoulder:b6,rightstick:b11,righttrigger:b7,rightx:a3,righty:a2,start:b9,x:b0,y:b1,",
    "030000009b2800008000000020020000,raphnet technologies 1-player WUSBMote v2.2,a:b1,b:b4,back:b2,dpdown:b13,dpleft:b14,dpright:b15,dpup:b12,leftshoulder:b6,rightshoulder:b7,start:b3,x:b0,y:b5,",
+    "030000009b2800006300000001010000,raphnet technologies Dual N64 to USB,a:b1,b:b0,dpdown:b11,dpleft:b12,dpright:b13,dpup:b10,leftshoulder:b4,leftx:a0,lefty:a1,rightshoulder:b5,righttrigger:b2,-rightx:b8,+rightx:b9,-righty:b6,+righty:b7,start:b3,type:n64,platform:Linux,",


Is there a better product string for this? Usually we put what's on the box instead of the USB descriptor string.

slouken · 2026-07-04T14:53:18Z


 bool SDL_IsJoystickGameCube(Uint16 vendor_id, Uint16 product_id)
 {
+    if (vendor_id == USB_VENDOR_NINTENDO && product_id == USB_PRODUCT_NINTENDO_GAMECUBE_ADAPTER)


This is already in the gamecube_devices list. Is there a reason you added this?

I started this PR two years ago before the gamecube controller had proper SDL support. This slipped my notice when rebasing.

slouken · 2026-07-04T14:53:34Z

    gamepad_button_small.png
    gamepad_dual_touchpad.png
+    gamepad_face_1234.png
+    gamepad_face_abcd.png


It looks like these are no longer used.

slouken · 2026-07-04T14:55:13Z

-            SDL_RenderTexture(ctx->renderer, ctx->face_abxy_texture, NULL, &dst);
-            break;
-        case SDL_GAMEPAD_BUTTON_LABEL_X:
+        switch (ctx->type) {


You're encouraging people to hard-code based on controller type rather than looking at what the label is for the face buttons. This means that this code will break when the PS6 controller comes out, where it wouldn't if you left it as-is.

slouken · 2026-07-04T14:58:18Z

I would suggest breaking this down into several PRs:

Adding the new controller types (what you have here looks good)
Adding the confirm/cancel gamepad actions (what you have here looks good)
Adding the additional button labels (I don't think this is sustainable, see my comments above)

hackleaf · 2026-07-04T21:46:57Z

I would suggest breaking this down into several PRs:

Ok, agreed.

slouken · 2026-07-04T21:50:00Z

I would suggest breaking this down into several PRs:

Ok, agreed.

As noted above, with the scope that you've defined for the labels, that seems like a good idea. Please document that scope in the header so it's clear what users should expect?

New gamepad types, button labels, get default confirm/cancel actions

8db1245

slouken reviewed Jun 27, 2026

View reviewed changes

nstbayless added 2 commits June 28, 2026 15:10

Simplify SDL_GamepadLocaleIsJP implementation

93590a2

Reduce/simplify new gamepad layouts and button labels

3a8a323

slouken reviewed Jul 4, 2026

View reviewed changes

	extern SDL_DECLSPEC SDL_GamepadButton SDLCALL SDL_GetGamepadConventionalActionButtonForType(SDL_GamepadType type, SDL_GamepadConventionalAction action);
	extern SDL_DECLSPEC SDL_GamepadButton SDLCALL SDL_GetGamepadActionButtonForType(SDL_GamepadType type, SDL_GamepadAction action);

		}
		else if (SDL_strstr(gamepad->mapping->mapping, "SDL_GAMECONTROLLER_USE_BUTTON_LABELS")) {

	}
	else if (SDL_strstr(gamepad->mapping->mapping, "SDL_GAMECONTROLLER_USE_BUTTON_LABELS")) {
	} else if (SDL_strstr(gamepad->mapping->mapping, "SDL_GAMECONTROLLER_USE_BUTTON_LABELS")) {

		if (gamepad->type != SDL_GAMEPAD_TYPE_NINTENDO_SWITCH_PRO
		&& gamepad->type != SDL_GAMEPAD_TYPE_NINTENDO_SWITCH_JOYCON_LEFT

		if (type == SDL_GAMEPAD_TYPE_PS3)
		return SDL_GAMEPAD_BUTTON_LABEL_SELECT;

Uh oh!

Conversation

nstbayless commented Jun 26, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Description

New Gamepad Types

New Gamepad Button Labels

"Conventional Actions"

DB Changes

Lingering Issues

Uh oh!

icculus commented Jun 27, 2026

Uh oh!

nstbayless commented Jun 27, 2026

Uh oh!

icculus commented Jun 27, 2026

Uh oh!

cgutman commented Jun 27, 2026

Uh oh!

Choose a reason for hiding this comment

Uh oh!

slouken commented Jun 28, 2026

Uh oh!

nstbayless commented Jun 28, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

nstbayless commented Jun 28, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

slouken commented Jul 4, 2026

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

slouken Jul 4, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

hackleaf Jul 4, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

nstbayless commented Jun 26, 2026 •

edited

Loading

nstbayless commented Jun 28, 2026 •

edited

Loading

nstbayless commented Jun 28, 2026 •

edited

Loading

slouken Jul 4, 2026 •

edited

Loading

hackleaf Jul 4, 2026 •

edited

Loading