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

Game branching on asset.party #3042

Open
trende2001 opened this issue Mar 19, 2023 · 9 comments
Open

Game branching on asset.party #3042

trende2001 opened this issue Mar 19, 2023 · 9 comments
Assignees
Labels

Comments

@trende2001
Copy link

trende2001 commented Mar 19, 2023

For?

S&Box, Other

What can't you do?

It would be great to have a main and dev branch of a game on asset.party.
Why? If you want to do an internal/external playtest of your game on your developer branch (on github for example), people will need to download your local game assets using your upload speed. If you have a lot of people joining, this comes down to a slow halt.

Developers along with you would also have to redownload all of the assets for your game if they want to check out what you implemented, s&box already assumes that you don't have the assets to that game and redownloads them, wasting time and space

How would you like it to work?

Uploading an experimental version of your game to a developer branch you create for your game on asset.party, having passworded branches, so on and so fourth. Kind of like betas and alphas before you all mash it into production

What have you tried?

N/A

Additional context

It would be genuinely awesome to download the developer version of the game from a blazing fast download server

@trende2001
Copy link
Author

trende2001 commented Mar 20, 2023

One thing: dedicated servers would be also able to switch between branches with +branch {main/dev}
If it's passworded, they would be able to access it with +branch_password {password}

@MrBrax
Copy link

MrBrax commented Mar 21, 2023

having to upload the dev branch to asset.party seems weird to me to begin with, can't run a dedicated server locally

@trende2001
Copy link
Author

if you don't have the +branch convar specified, it would default to the production (main) branch

@SplatzyXD
Copy link

Would really help out in game testing.

@garrynewman garrynewman self-assigned this Mar 22, 2023
@trende2001
Copy link
Author

trende2001 commented Mar 22, 2023

yeah, i believe there could be a second option to link the github repo of your game and it would pull all of the branches from there, though you could choose to exclude a few branches from being shown if you'd like

@matekdev
Copy link

matekdev commented Apr 5, 2024

I'm actively working on a major overhaul to our systems in My Summer Cottage. One of these includes changing the structure of our game resources. Due to this, I'm unable to test locally anymore since the second client will always download the asset party version of the game resources.

I can obviously re-upload to asset.party, however, this will break the live version of our build. Basically, I will have to break the live version of our game once in a while in order to test.

It'd be nice to have branching for this use case.

@MrBrax
Copy link

MrBrax commented Apr 5, 2024

It'd be nice to have branching for this use case.

in addition to this, invite-only play permissions would be useful for the entire game or branches

@matekdev
Copy link

matekdev commented Jun 28, 2024

This is still a massive pain point.

Local multiplayer testing pulls all resources from the live build. So you are unable to do any testing locally without uploading to the live copy.

Either build branching needs to be introduced or local multiplayer testing should pull from your local copy.

@garrynewman
Copy link
Member

We have a plan for this, but branching isn't really the solution to testing locally. When testing locally those games should work regardless of being on asset party or not.

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

No branches or pull requests

6 participants