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

Additional itch.io options. #3

Open
1 of 5 tasks
Chaser324 opened this issue Jan 27, 2017 · 5 comments
Open
1 of 5 tasks

Additional itch.io options. #3

Chaser324 opened this issue Jan 27, 2017 · 5 comments

Comments

@Chaser324
Copy link
Collaborator

Chaser324 commented Jan 27, 2017

There are some additional flags available through the itch.io butler command line tool that should probably be surfaced as options.

  • --verbose - Provides additional details about push operation.
  • --identity="PATH_TO_CREDENTIALS" - Allows user to specify path to a specific itch.io API token. Might be nice for people that upload to multiple accounts.
  • --ignore=IGNORE - Glob pattern of files to ignore.
  • --userversion=USERVERSION - Since users might already be generating a version number with SuperUnityBuild, they might as well pass it to itch.io for the sake of keeping things consistent.
  • --beeps4life - Butler emits a system beep when starting a task. BEEPS 4 LIFE.
@XaeroDegreaz
Copy link

XaeroDegreaz commented Mar 3, 2017

--userversion=USERVERSION

Looking forward to this. Came here to suggest this myself.

In the interim, should something like:

scriptArguments.Append(string.format("--userversion {0}", BuildConstants.version));

work when adding it to the UploadItch.cs work?

Great asset by the way, many thanks.

@XaeroDegreaz
Copy link

Actually that works quite well. I added it to line 65

scriptArguments.Append( string.Format( " --userversion {0}", BuildConstants.version ) );

@Chaser324
Copy link
Collaborator Author

Chaser324 commented Mar 3, 2017

Added "--userversion" option in the latest commit.

@Chaser324
Copy link
Collaborator Author

Chaser324 commented Mar 3, 2017

Also, I just want to note that it's best to not reference BuildConstants at build-time. It's primarily intended for accessing that data in your game at run-time.

Unfortunately, I don't have a great interface at the moment for accessing that data at build-time, but most of it is accessible from the arguments passed into Execute or PerBuildExecute or by directly accessing BuildSettings - the version string for instance can be found in BuildSettings.productParameters.lastGeneratedVersion.

@XaeroDegreaz
Copy link

Thanks for the clarification on that. I knew there must be a better way.

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

No branches or pull requests

3 participants