Play seele together!!!๐๐๐
SEELE AI is officially introducing its Creator Program, which includes several incentives. If you are interested, please DM me.
Neon streets, quick lane changes, and bright pickups keep this vertical runner readable at a glance. A real gameplay reference in the SEELE AI creative library.
A checkout test should not end at 'payment failed.' Retry the same purchase after reconnecting, then confirm the player balance and entitlement cannot diverge. For an indie game store, the recovery path matters more than the happy path. Which state do you persist first?
Nagi can win without trying. He just admitted he canโt win without you. How do you answer? Try this unofficial, fan-made AI roleplay: https://t.co/FNFxsCG5Zp
Levi blocks the exit, takes your hand, and waits: will you follow? Enter this unofficial, fan-made AI roleplayโno affiliation or endorsement. Answer him on SEELE AI: https://t.co/JmyVWoTAwJ
@Dexerto The free game makes the chocolate the first monetization layer. If it reached 30k plays, would you keep it as brand-funded acquisition, add ads, or test a small cosmetic purchase to see whether the game can stand on its own?
For Cocos creators adding in-game purchases, where does the real friction live: designing the item, wiring the store UI, handling payment failures, tracking player balances, or getting creator payouts right? Curious which part consumes the most time. #CocosCreator
If you're building a game and the bottleneck is 3D assets, this repo is useful.\n\nIt groups AI game-dev tools by pipeline stage, with a solid 3D asset section: Meshy, Tripo3D, Rodin, InstantMesh, TripoSR.\n\nhttps://github.com/SeeleAI/awesome-game-dev-ai
A playable beats a pitch deck when you need real feedback.
Describe the game, get a playable version, and see what people actually react to.
Try it:
https://t.co/dhYwGxGVyj
A playable proves the idea faster than a pitch deck.
Seele turns game ideas into something people can actually try.
Try the playable now: https://t.co/4aH07fQGuu
#AIGame#Playable
@jiaqing_xie Nice direction. One adjacent OSS problem: once a skill library grows, you need a way to see overlaps and routing ambiguity across the whole landscape. We open-sourced skill-taxonomy for that: https://t.co/kqRgUePJ39