Closed CelaldoganGunes closed 1 year ago
Thank you for the suggestion, but we won't be making this change to the code base. Leaving the AuthSessionTicket in it's original form allows for working with it in a more flexible way.
From what the image describes, the hex encoded UTF-8 string of the ticket should be sent as an HTTPS from your secure server so this has nothing to do with steamworks extension itself you can still follow the workflow:
Hello, As it is written in Steam API Docs, to be able to use the ticket that is received fromISteamUser::GetAuthSessionTicket, we need to convert it to a hex encoded UTF-8 string.
Current version of the extension gives us a buffer but it is not in the required format. I edited the extension again and it gives us the ticket in the right format. And we can send this ticket directly to the Steam without editing it in GameMaker. I don't know how to send you my code, so I am creating this issue. I am not good at C++, because of that you may need to optimize some areas. I am waiting for you to add this to the extension, then I will test it in my macbook. (I developed this in my Windows computer and I don't know how to build dylib files.)
` HAuthTicket authTicket; YYEXPORT void steam_user_get_auth_session_ticket(RValue& Result, CInstance selfinst, CInstance otherinst, int argc, RValue arg)//(char data, double size) { static const uint32 MAX_TICKET_SIZE{ 1024 }; uint32 ticketSize{ 0 }; uint8 ticket[MAX_TICKET_SIZE];
}`
GameMaker Code:
var _buf = steam_user_get_auth_session_ticket(); AuthSessionTicket = buffer_read(_buf,buffer_string)