Game SDK - Outdated Activity Struct

[Vercidium]

Description

Hey all, I created this issue last year and it was moved to the Discord GameSDK repository, which has now been archived.

Is Discord moving away from gaming and focusing more on the social side of things?

The Discord GameSDK was last updated in September 2020 (v3.1.0) on the Discord Developers Discord server, and there are still outstanding issues with the game overlay, voice chat and SDK compilation issues.

Steps to Reproduce

Run this code:

var activity = new Activity();
activity.State = "Playing Sector's Edge";
activity.Timestamps.Start = (int)discordStartDate.Subtract(new DateTime(1970, 1, 1)).TotalSeconds;

activity.Party = new ActivityParty()
{
    Id = "partyidentifier",
    Size =
    {
        CurrentSize = 4,
        MaxSize = 16
    }
};

// This line here causes the InvalidPayload error
activity.Secrets = new ActivitySecrets()
{
    Match = "match abc",                
};

activityManager.UpdateActivity(activity, ActivityCallbackMethod);

Expected Behavior

The Activity payload should be sent successfully and an ok result returned.

Current Behavior

An InvalidPayload response is provided. This is because the Activity struct in the provided game SDK is outdated and does not contain the Privacy field.

Screenshots/Videos

No response

Client and System Information

Desktop client (not Canary or PTB): Stable 128323 (5628003) Host 1.0.9004 Windows 10 64-Bit (10.0.19043)

[MaskDuck]

well... the discord gamesdk was discontinued :( wait nvm looks like i misread

[Vercidium]

I saw SKUs were discontinued but didn't think that included the whole GameSDK as well. Is there another way to set rich presence and send lobby invites?

[MaskDuck]

not sure about lobby invite, but if you wanna set rich presence then you can use rpc

[AlmostSuspense]

the game SDK hasn't been deprecated, only store pages and commerce were

[night]

is this solely a documentation issue? have you tried passing privacy into the party struct?

[Dids]

The SDK hasn't been updated in quite a while, at least according to the version number/link in the docs, and there's still no ARM64 support. Seems pretty abandoned to me.

EDIT: Turns out that the versioned releases linked here are old, however I still had the latest release link lying around, and judging by the contents of it, it has indeed been updated, including with support for ARM64/AARCH64/M1 SoC.

Now my question is, why has development continued on the SDK, but nobody bothered to update the documentation?
Or did they simply stop doing versioned releases and are going with a "bleeding edge" release strategy instead? Because if so, that's not great news either.