Page 1 of 1
(Resolved) Dice forge bug already fixed in big extension update
Posted: 16 June 2020, 05:06
by jjcf89
I thought I would try to get my toes wet by fixing up this Dice Forge bug.
"CAN WE HAVE AN INDICATION THAT WE HAVE A SECOND HAMMER"
https://boardgamearena.com/bug?id=10287
However, when I made a copy of the game it looks like the devs have already fixed it. But it never got released, likely because the expansion work they are working on hasn't been finished yet.
How is this best handled? If there is no imminent release of the expansion, could I be given a copy of the game that is in production and then I or devs could copy the fix to be released sooner?
Just looking for ways to help. Perhaps all that needs to be done is for the bug to be acknowledged with a status so new devs don't waste their time looking into it.
Re: Dice forge bug already fixed in big extension update
Posted: 16 June 2020, 13:06
by docthib
Hello,
I was wondering what was the 'diceforgebugfixtwo' project
You're right, most of the suggestions / bugs have been fixed recently in the studio project (which contains the work on expansion).
Just need some more QA on these before releasing the patch.
About the current prod version, I don't know how we can retrieve it

Need to get some info on this.
Anyway thanks for trying to help. I'll update the reports soon (and keep you updated).
Re: Dice forge bug already fixed in big extension update
Posted: 16 June 2020, 14:32
by jjcf89
Cool, note I also created a diceforgebugfix project but it never showed up on my control panel so I couldn't start a game of it. I guess both could be deleted
You're right, most of the suggestions / bugs have been fixed recently in the studio project (which contains the work on expansion).
Just need some more QA on these before releasing the patch.
Any chance of updating the bug, its in the top 10 or 20 of the bug hunt page.
Re: Dice forge bug already fixed in big extension update
Posted: 16 June 2020, 17:30
by jjcf89
Saw your update, thanks.
Re: Dice forge bug already fixed in big extension update
Posted: 16 June 2020, 22:34
by Inaofr
docthib wrote: ↑16 June 2020, 13:06About the current prod version, I don't know how we can retrieve it

Need to get some info on this.
First if you don't have one do a backup of your current version.
In your control panel in the studio, you have a list of "Versions available for production". Copy the full version number of the one you want to retrieve (ex: 200614-1423), paste it instead of "head" in the field next to "Overwrite working copy with this revision" and click on the button (you may have to remove the -, not sure anymore).
You can now download through sftp the old version.
I advise you to setup a git repository and to put into it all the versions you find useful to have. It is a lot more convenient than using just the control panel, and I think safer.
Re: (Resolved) Dice forge bug already fixed in big extension update
Posted: 17 June 2020, 08:53
by vincentt
Hi,
The installation in production is quite tricky.
I did one last year...
We are going to release an alpha soon with a part of the extension, with Docthib we will work on releasing the prod version without the extension at the same time.
About the bugs some are already fixed, but same thing.
We are currently looking into the last big bugs to check if they are fixed
Cheers
Re: Dice forge bug already fixed in big extension update
Posted: 17 June 2020, 13:05
by docthib
Inaofr wrote: ↑16 June 2020, 22:34
First if you don't have one do a backup of your current version.
In your control panel in the studio, you have a list of "Versions available for production". Copy the full version number of the one you want to retrieve (ex: 200614-1423), paste it instead of "head" in the field next to "Overwrite working copy with this revision" and click on the button (you may have to remove the -, not sure anymore).
You can now download through sftp the old version.
I advise you to setup a git repository and to put into it all the versions you find useful to have. It is a lot more convenient than using just the control panel, and I think safer.a
Thanks a lot! That was quite tricky indeed

You don't need version number but revision number which is only available in "Commit log" (and you only need the numbers 'r12345' only keep '12345').