Skip to content

Conversation

@thisis2838
Copy link
Contributor

Some early steampipe builds use the typical version number print like pre-steampipe which does not work with the version command backtracing method (at least at the time of writing).

Some early steampipe builds use the typical version number print like pre-steampipe which does not work with the version command backtracing method (at least at the time of writing).
@UncraftedName
Copy link
Contributor

If you're printing out msg/warning that aren't directly caused by user input (in this case there's other features which might get the game build programmatically), then you should do something like Warning("SPT: ...");.

@lipsanen lipsanen self-requested a review January 22, 2026 15:22
Copy link
Collaborator

@lipsanen lipsanen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice stuff, small nitpick along the lines of what Uncrafted said

@evanlin96069
Copy link
Contributor

When the environment variable SPT_USE_BUILD_NUMBER is set, we should not search the build number at all.
My bad for not implementing it properly back then. Can probably also fix it here?

@lipsanen
Copy link
Collaborator

lipsanen commented Jan 22, 2026

When the environment variable SPT_USE_BUILD_NUMBER is set, we should not search the build number at all. My bad for not implementing it properly back then. Can probably also fix it here?

someone ™️ can do this in another PR

@lipsanen lipsanen merged commit 0e35414 into OutOfBoundsOffice:master Jan 22, 2026
8 checks passed
@lipsanen
Copy link
Collaborator

tyvm

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

Successfully merging this pull request may close these issues.

4 participants