Login Widget
Collects username and password, then calls the BFAT login action.
Unreal Connection
This page explains the BFAT game connection concept without showing private infrastructure details.
System Flow
Unreal Widget
BFAT Plugin
WordPress API
Wallet Data
Unreal UI
Blueprint Information
The Unreal side uses login widgets, player menu widgets, wallet refresh, inventory actions, store actions, and room actions. This page shows concepts only, not code.
WBP_BFATLoginUsername, password, login action
BFAT PluginSession, token, wallet request
WBP_PlayerMenuCoins, inventory, rooms
GameplaySolo online, public room, private room
Unreal Blueprint Setup
Information view of the Blueprint pieces used by the BFAT login and player menu flow.
Wallet Update
After login, the widget asks BFAT for current wallet information.
Player Menu
Displays username, coins, inventory, store, online rooms, private rooms, and logout.
Gameplay Menu
During gameplay, Esc can show or hide the player account menu.
Other Engine Connections
BFAT can support other engines when they use the same account, wallet, inventory, and room concepts.
Babylon.js Connection
Babylon.js games can connect to BFAT through browser-based requests. The game can show login UI, store account session data, display coins, request inventory, and join online or private room flows.
Babylon.js UI
BFAT Web Connector
WordPress API
Wallet / Inventory / Rooms
GameMaker Connection
GameMaker games can use BFAT as an external account service. The game sends login requests, receives player account data, displays wallet coins, and uses room information to move into online gameplay.
GameMaker UI
BFAT HTTP Layer
WordPress API
Account / Coins / Rooms
Player Journey
The same account flow can support solo gameplay first, then multiplayer choices through the player menu.
Login
Player signs in through BFAT login UI.
Wallet
Coins and account data are shown in the game UI.
Menu
Esc opens the player account menu during gameplay.
Rooms
Player chooses online, private room, store, or inventory.