@Lag_Ninja@start1up_fgc@EskayOW This is a novel feature for newbies. What’s cool, is what drives this: a set of 350+ FG symbols as web/js components for every FG/controller. So a major feature is players can document their lab combos… with symbols best for their brains. Faster memorization with science! 🤌
@OmegaTomHanks@start1up_fgc Hi OTH!
I’m lead dev, and am working non-stop on the app rn to tidy up + add final features for players to get true value from the tools.
Once players use this, they aren’t going to want to take steps back! So i am crunching myself daily to get it ready for real time use/users!
Shoutout to @Mavercade the post below is 🤌! The current lineup is in & the split modular KeebWarrior was a cool challenge!
Our app is setup to help users keep track of fight stick use per match/game. So we had to enter each KW pair to cover all possible user pairs! 🤩😍😎
The inspiration for this was the issue pinning feature in @github !
Those pins help us build massive stuff like Start1up!
So now our goals follow the same flow, but we had to do it without drag and drop (for touch I/O users).
This was satisfying to implement!
#start1up
We’ve added pinning and ordering to our #FGC goals system! Soon it will be easy for everyone to keep track of everything they’re aiming for across all of their favorite fighting games and fighters!
#streetfighter#TEKKEN#fatalfury#MortalKombat
We actually hit the scale wall and needed to review the entire app as far as how to keep the feel of browsing purely fighting game content, but not sending too much #FGC data down the pipe at once.
But we’ve found a good middle ground that’s consistent across devices! B2W!
Here’s where the #start1up web app for the #fgc is at, as of today:
62 FGC Platforms
167 Franchises in the FGC
445 FGC games
1,731 FG Characters
26 FGC Fighter Archetypes
50 Fighter Homelands
43 FGC Fight Sticks
351 FGC Notation Move Symbols
It’s wild tbh. I did the VainGlory tool app at first to just stress test my new Bootstrap 4 extended library. That was shockingly well received, but sadly I didn’t have the man power to update the dang data for each game update. Unscalable :(
So this #FGC app, is VERY scalable!
Here’s where the #start1up web app for the #fgc is at with historical data as of today:
58 FGC Platforms
165 Franchises in the FGC
340 FGC games
1,599 FG Characters
26 FGC Fighter Archetypes
49 Fighter Homelands
43 FGC Fight Sticks
338 FGC Notation Move Symbols
We still have a bunch of fighting game fighters to add, so there are many more Terry’s coming… but it’s pretty cool to see this history of #fgc Terry’s in the #start1up system so far in the meantime!
It’s getting closer!!!
Our internal goal is to get our combo tooling set for each game in the #fgc circuit, starting with #Evo2025!
It’s a painstaking process, but once we’re over the hump of making thousands of combo symbols - specific to each game - it’s COMBO time!
A capture from our local dev version of the app so far!
Our mission is to help the #fgc grow and help new player to git gud faster and seasoned players to stay gud longer!
#start1up
So that leak that's been now un-leaked prodded us to finally go ahead and get the app data in place for the upcoming Fatal Fury: City of the Wolves release in April!
Here's a peek of the new COTW game view:
Here's a peek at our upcoming genre-level FGC player profile.
We're looking at a Q2 beta release, so any ideas, questions, and requests are welcome and could get put into work in the meantime!
@MichaelThiessen Hope to get health insurance tbh. Vue isn’t the smartest choice for that goal granted, but it would have driven me nuts to make a lib for react when I prefer vue so much more. So for now, just gotta keep swimming.
@vainglory instantly with the fold back to its aesthetic glory, I’m inspired to rebuild the tools site with modern js tooling, login/saves, and the tourney system I always wished I had built. Plus open up the stat data to invite theory crafters back. Just sayin… VG is GOAT
Often I find that I'm copying prop types from a child @vuejs component just to use them in a parent component.
But I've discovered that *stealing* those prop types is much better than just copying them.
For example, we have an `Icon` component being used in this component: