Just wanting to check if I’ve missed something but why are people making a big deal of the upcoming BO1/BO2 ports when they’re been available to play on Series X etc for years since they became backwards compatible and has been available to purchase on the marketplace for years also?
Can somebody confirm for epic fluoress the combo is a blowt + gob?
I’m on my 30th gob at this rate with all 10 torches each time too!
This games luck sometimes 😭
Anyone else tired of putting consistent work on the various clubbox acts over the last few months just to be met with terrible ticket luck time after time again?
Particularly this current act, I’ve maximised as much as I can (all standard islands + 1 mirror, all with double breeding + nursery stations + all monsters) and yet I’m on 30/38 track wise and definitely won’t be getting the new legendary, let alone Hornacle despite being near consistent with the game timing wise
I feel a huge part of this would be solved with 1) better odds on the wheel (I get that’s part of it but too often is it the lowest roll) and 2) replacing sticker packs with additional tickets if the album is completed)
In my case, I reckon I’d definitely have completed this act if all the literally useless packs collected since the album was completed were instead converted to tickets!
Thought I’d share this to help anyone else who may have gotten to the same dead end I did originally regarding the limitation in the inbuilt walkthrough feature.
As great as it is that FF has this feature built in for ease, you’ll quickly find it’s very limited in that it won’t scroll (so if your walkthrough is on a long page it won’t scroll down to it and will be off screen) or if you need anything advanced such as opening a drawer to then detail through the drawer options, the inbuilt FF won’t do this.
Equally, FF makes it near impossible to use custom actions/widgets to interact directly with FF widgets as no global keys get exposed to feed in.
I was about to give up when I came up with what so far is actually looking and working pretty good:
duplicate the page(s) you want the walkthrough on
trim down all the backlog excess and keep it purely UI, this page is purely for the walkthrough so keep it as lean as possible on all the added actions, database links etc
click “view code” to get the full page FF code
go to any AI agent of your choice (note if page code is super long you may need higher limits or to find an AI agent that allows more characters) and ask it to create a custom FF widget matching strictly just the design and keep it as lean as possible (for mine it turned 5000 lines to a 900 code widget) and also pass it the boilerplate code as a starting point to ensure it is compatible with FF’s custom widget expectations
then test and check if it looks like your actual page
now use the tutorial_coach_mark package (FF will auto import this into your project if you’ve created at least one walkthrough so do that if it doesn’t appear in your dependencies) with AI and ask it to add whatever walkthrough steps you want into that custom widget
once happy, simply add some conditional on page load checks to determine whether or not if first time or not etc to navigate to the dummy walkthrough page or the genuine page (at the end of the walkthrough your custom widget can auto navigate to the real page)
Is this a big work around ? Yes of course, but does it work and gives you a lot of flexibility to achieve the walkthroughs you actually want for your users, 100%
Hope this helps people!