Poking this thread.
Clearly the fgi is not the code our games are using unless we haven't used
the roll code boxes in ages (see PR https://github.com/Dulux-Oz/FGI/pull/10
).
The main motivation for someone contributing to this project is to help our
games. It needs to be very obvious to someone playing in Deadlands or Star
Frontiers how they can fix a bug or automate something that is hindering
them in their game.
I think that we're in the weeds ATM trying to make the perfect die roller
but we're neglecting the greater product and the reason that folk want to
help out. You can capture my attention for a bit a tricky technical problem
and mess to clean up, but even that only goes so far, lol.
Getting our ruleset code in FGI so we can see the games layered on top so
that we can see the API between them is super important for everyone seeing
the big picture and vision. But also important so that people can see that
the effort they spend can have an immediate effect on everyone's gaming
time.
I keep saying this, but shelving all work on the UDR until we have
Deadlands using this code and working is my top priority. If you want to
just commit broken code to a feature branch I'm happy doing the leg work
trying to integrate things and fix bugs.
How much effort is required to yank that code out from wherever it is and
put it in here (or a separate repo)?
On Tue, 1 Sep 2020, 12:30 Ben Kolera, <ben.kolera@xxxxxxxxx> wrote:
The desktop code UI is borked in develop because the controls are never
registered with the managers. I just lost an awful lot of lunchtime hacking
time trying to figure out how I broke things to realise they were broken
before I got here working on the assumption that this was what was already
working in our games, lol.
(Attached is a Debug.chat of aRoll right before the return of
setRollCodesFromDesktop
https://github.com/Dulux-Oz/FGI/blob/master/DORCoreMin/UDR/Scripts/lsUDRDieManager.lua#L1120
)
What's the migration plan to get our games running on the results of our
work here?
