Patching Builds? #7
Labels
No Label
bug
Critical Priority
duplicate
enhancement
help wanted
High Priority
Low Priority
Medium Priority
Meta
needs more info
question
refactor
wontfix
bug
Critical Priority
duplicate
enhancement
help wanted
High Priority
invalid
Low Priority
Medium Priority
Meta
question
wontfix
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: Cavemanon/SnootGame#7
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Some anons have complained about having to re-download a build once its released and rather just be able to patch it. If there's a way to do this that is both easy for techlets to do and easy for us to make, that'd be great. Ideally, this would be cross platform: GNU/Linux, *BSD, Windows, MacOS, Android, maybe even IOS, but if we can only fix desktop this way, that's fine.
Hi,
Are we looking to have standalone files for potentially any version to any version or should we do an update service-type of thing?
E.g. there would be a check in the game for a version on the server (whatever content server there is), if it is newer than the one reported on the end machine then check components and redownload parts marked as new version.
That's about as comfy as it can get. Though, there are drawbacks.
Not sure if a standalone patch file would be reasonably easy to implement without it containing the actual game itself. If this bit isn't an issue, and we just want a file that can detect (or be told where to expect) the folder for the game and replace things as necessary from the carried payload that's relatively easy. As multiple versions start to circulate, not having the entire game in the patch file would create scenarios perhaps where for an installation with patch level 5, file A1 needs to be replaced by file A3 for the current patch file 7, but A3 needs file B2 instead of B1 - however B2 was patched in patch file 6. Unless we do a cummulative patch (but that will have a steady size increase as well eventually).
As for the versions... Just a thought, say the writing changes and people say I liked version X way better. Will older versions remain available?
[OFF TOPIC] And finally, do we have a discord channel, irc, telegram, forum, etc for general chatter and questions? Or is it email only?
looks like renpy does offer built-in functionality for option B (an update server)
https://www.renpy.org/doc/html/updater.html
we could essentially implement an update server alongside renpy's built in functionality, add some functionality to the main menu ala an "update" button that would call the appropriate functions, make what would hopefully be the "final manual release" for download, and boom - now whenever we push updates to the code can be done entirely in game
@Nio your concerns are correct in how patch files work (I was worried about a similar issue). Though, since renpy has an updater this likely will be the method we go. I can set up snootgame.xyz to have everything we need soon enough. Will need to look into the documentation for this soon enough. Anyone wanna go ahead and add an update button to the Help&About menu? (soon to be extras menu due to https://git.snootgame.xyz/PrincipalSpears/SnootGame/pulls/14)
btw @Nio we do have a private way of communicating (a matrix and discord), but the other guys keep tight control over who gets in and out. Mostly due to fears of ko-op shittery, doxing, someone leaking assets, etc. If you want in, contribute some and show that you got skill and can be trusted. Nothing personal behind that, its just the tight security needed to keep us from being BTFO'd.
Nice, being new to Ren'py I didn't even assume it would have something like this. But saves some of the work.
@coolestskinnieinthejungle , @PrincipalSpears if you all are cool with it, I would like to take a shot at this.
And @PrincipalSpears , I completely understand the worries associated with this. All good. I will work on earning my place.
I got SSH access to the VPS that runs this stuff and am used to sysadmin stuff. Will get this set up backend wise. If anyone wants to give a shot for setting this stuff up for the game updater client, then go for it. Will create a branch for this stuff
👍
Started working on this in https://git.snootgame.xyz/Nio/SnootGame_w_ExtrasMenu which also addresses https://git.snootgame.xyz/PrincipalSpears/SnootGame/issues/19 (and added the ico file as well, it's so minor, I didn't think it is worth creating an entirely separate fork).
I can also work on buttons if you need me to. I have a few things at my disposal, way back when I used to draw. I should get back into that again, now that I think about it.
Cool, will start working a bit on that then
MichaelYick referenced this issue2021-06-15 09:54:40 +00:00
bro this ain't even done yet lmao
why the fuck did it close the issue wtf lol
nutbuster referenced this issue2021-07-03 07:03:14 +00:00
DONE
fucking renpy documentation