Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Plans/Ideas/Thoughts #4

Open
trdwll opened this issue Nov 12, 2020 · 5 comments
Open

Plans/Ideas/Thoughts #4

trdwll opened this issue Nov 12, 2020 · 5 comments

Comments

@trdwll
Copy link
Owner

trdwll commented Nov 12, 2020

In general, I want this to be as close to a 1:1 as much possible. However, maybe a branch for a light version with methods renamed or even do that as the main branch? (for example BLoggedOn renamed to IsLoggedOn etc)

Remove unnecessary params. I've already done this and have been, but it's possible that I've missed some. (this could be stuff like bufferlen - where we can just pass MAX_uint32, etc instead)
Re-evaluate whether methods should be const or Pure. (ie (BlueprintCallable, BlueprintPure=false) or (BlueprintPure))
Determine what methods should be async if any or even if the entire library should be converted to async. Possible future plan? Facepunch.Steamworks does this.
Convert timestamps (int32/uint32) to FDateTime for easier management?
Convert for loops to range-based for loops where it makes sense.

Add a project to test functionality and to show examples of how to implement things.

What else? Let me know your thoughts.

@ApostolosBouz
Copy link

ApostolosBouz commented Jan 21, 2021

Personally I am totally on-board with the 1:1. Unfortunately (in my experience) most developers are unfamiliar with the internals of steam SDK.
For those folks, a "light", more callback-compacted branch might be more useful. I'd say, keep up with 1:1 for the time being and when everything is mapped appropriately (hopefully with the aid of other contributors), then decide what to compact to bigger functions further down the line.

@devinjdawson
Copy link

How much of this overlaps with AdvancedSessions and AdvancedSteamSessions? Is it alright to keep both plugins installed?

@trdwll
Copy link
Owner Author

trdwll commented May 11, 2021

How much of this overlaps with AdvancedSessions and AdvancedSteamSessions? Is it alright to keep both plugins installed?

I'm not familiar with those plugins. SteamBridge is a wrapper for the entire Steamworks API.

@devinjdawson
Copy link

devinjdawson commented May 11, 2021 via email

@unclemusclez
Copy link

unclemusclez commented May 28, 2021

Is there an easy way to generate a dummy set of "SteamFriends/GetSteamFriends" data within the editor, and if not, would you consider adding it to the plugin? I am trying to create test data so I can troubleshoot friends lists within the PIE editor, but it has become a project in itself trying to replicate some of the functionality in blueprint. It would be nice to generate random sets for the other get functions like SteamApps, SteamUser, etc., as well.

That being said, a better solution I have come across would be to link SteamBridge to Editor Preferences -> Level Editor -> Play Credentials, if possible. I have found very little documentation on the Play Credentials being utilized successfully, and most responses lead to the subsystems aside from EOS being disabled in PIE.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants