After some experience with BYONDexe and having assistance, I would like to make a proper request for a repair feature that can be clicked on to perform any necessary replacements (which could be handled through a re-extraction process that already happens when you first click on the executable).
Currently, I have seen it re-extract most files except for 'hub.zip' (which I understand for the latter and y'all have mentioned it before). However, I think it would be handy to let it re-extract at least the 'hub.zip' for local installations or even the whole thing again (in case issues popup).
Now, I am not so sure how hard it would be to implement a repair button (which I know may affect the current releases of BYONDexe) in the cases you need to correct anything wrong with it. It is an optional feature since y'all don't have to include it (if y'all have reasons for not implementing a repair feature). I just thought it could make it possible to repair the standalone executable game directory (when it installed to BYOND/bin/author/hub).
ID:892094
 Jul 26 2012, 9:09 pm
|
|||||||
| |||||||
|
#1 Jul 26 2012, 10:00 pm
|
|
Tom
 |
Seems to me that we should be updating the hub.zip on new releases, so I'm not sure if this is really a feature request or bug report.
|
|
#2 Jul 26 2012, 10:20 pm
|
|
Reason why I thought it would be a request is because I remember reading in the 'README-CONFIG.txt' file that 'hub.zip' gets deleted after it is unzipped and installed. However, there might be a few cases if you deleted said hub entry through uninstallation where you need to repair it (instead of having to delete the folder to reextract 'hub.zip' again).
| |
|
#3 Jul 26 2012, 10:26 pm
|
|
I'm not sure what you mean by "repair". It sounds like you want to overwrite/re-extract hub.zip on new exes after you update it, is that right? I'd think it would work that way by default. The deletion of hub.zip just means that the file doesn't stick around after it is extracted.
| |
|
#4 Jul 26 2012, 10:36 pm
|
|
Updating does fix it if provided. However, it currently only works if a new version is out (or when the version on the hub is changed). I only encounter the issue when one uninstalls the hub by using BYOND client (which rarely anyone does, though some people still uninstall and try to reinstall later).
The 'join' button stops showing up (due to no longer finding a local install). In order to restore it, you must currently delete the game executable directory to re-extract from the 'hub.zip' or simply have a copy of the updated zip (which should do the same). Now thinking about updates, I think the update feature could work for the repair feature. Update-style Repair Setup: 1. Click on the included Repair Button (it could be disabled for games that do not support local hosting.). 2. Get a prompt to perform the repair based on the update zip. 3. Repair through the update zip is performed and you get access to local game hosting again. | |
|
#5 Jul 26 2012, 10:39 pm
|
|
Honestly, I really don't understand the issue. Can you just give me a step-by-step example of what you are doing and what the problem is?
| |
|
#6 Jul 26 2012, 10:51 pm
|
|
Sure thing. Here are the steps to make the local game installation no longer show up:
1. Run the standalone executable for the game if it is your first time (provided it installs from the 'hub.zip' to create a local installation). 2. Close it 3. Run the BYOND client. 4. Uninstall the hub entry through the client (can be done on hub-installed copies as well as executable-installed copies). 5. Run the standalone executable again. You will find a completely missing 'join' button. 6a. To restore the 'join' button, close the executable and delete the directory based on the 'BYOND/bin/author/game' format. 6b. The 'join' button for local games can also be restored by waiting for an update or simply running from an update zip (if you possess at all). 7. Run the standalone executable again. You got yourself a fresh brand new copy and therefore reenabled the 'join' button. | |