How tranek/gasshooter works
Project type and purpose
• GASShooter is a UE4 sample game project (FPS/TPS) built on the GameplayAbilitySystem (GAS) plugin.
• It demonstrates advanced GAS techniques: equippable weapons, ability batching, targeting (TargetActors/Reticles), custom GameplayEffects, attribute sets, GameplayCues, UI integration, AI, and replication.
File structure
• Root files:
• GASShooter.uproject – ties together modules, plugins, content.
• Config/Default*.ini – engine/game/editor configuration.
• LICENSE, README.md
• Content/ – all game assets, organized by functional domains:
• FPWeapon – reusable weapon materials, meshes, textures
• GASShooter – Blueprints (GameMode, Characters, Abilities, UI, Items, Weapons, Maps, Effects)
• InfinityBladeFireLands & ShooterGame – third-party Epic assets used for visuals/audio
• Source/ – C++ code split into two modules:
• GASShooter (runtime)
– Public/ & Private/ folders with core game classes: GameModeBase, PlayerController/State, Characters, AbilitySystemComponent, Abilities, AttributeSets, GameplayCueManager, Weapons, Items, AI, UI Widgets
• GASShooterEditor (editor-only targets)
• Build scripts & target files: .Target.cs, .Build.cs
Pulling insights from the README
• Confirms UE4.27 + GAS plugin, not production ready but a rich learning sample.
• Enumerates key GAS concepts covered and input bindings.
• Shows mapping of weapons to abilities (Primary, Secondary, Alternate).
Main components
a. Unreal Engine Core & Editor
b. GAS Plugin Subsystem (AbilitySystemGlobals, ASC, GameplayAbility, GameplayEffect, GameplayCue)
c. GASShooter Runtime Module
– GameModeBase
– Player Subsystem: PlayerController → Character (GSCharacterBase) → AbilitySystemComponent → AttributeSets
– Abilities & AbilityTasks (GA_*, AsyncTask*, GSAT_*)
– Weapons & Projectiles (GSWeapon, GSProjectile)
– Items & Pickups (GSPickup)
– AI (GSHeroAIController)
– UI (GSHUDWidget, DamageText, StatusBar, Reticles)
d. Content Assets (Blueprints & DataAssets)
– Drive configuration and tuning of C++ systems
e. Config & Build Scripts (initialization)
f. External Modules (ShooterGame, InfinityBlade assets)
Relationships & interactions
• Startup: Editor/Engine reads uproject → loads GAS plugin + GASShooter module → reads Config.
• At runtime:
1. GameModeBase spawns PlayerController
2. PlayerController possesses GSCharacterBase
3. GSCharacterBase houses an AbilitySystemComponent (ASC)
4. Player input → invokes ASC to activate GameplayAbilities (Primary/Secondary/Alternate)
5. GameplayAbilities issue GameplayEffects against AttributeSets → modify Health/Mana/Stamina/Ammo
6. GameplayCues trigger VFX/SFX & update UI Widgets
7. Physics & Projectiles handled by GSProjectile, collisions feed back into GAS via GameplayEffects
8. Pickup actors (GSPickup) apply Effects on overlap
9. AIController uses ability and movement components to drive NPC behavior
• Blueprint assets mirror and extend C++ classes for rapid iteration.
Architectural patterns & design principles
• Modular C++ modules for runtime vs. editor
• Component-based (Actors + Components, esp. AbilitySystemComponent)
• Data-driven: Blueprints/DataAssets configure C++ systems
• GAS pipeline: Input → GameplayAbility → GameplayEffect → AttributeSet → GameplayCue
• Separation of concerns: Input/Controller, GameLogic (GASShooter module), Presentation (UMG/Blueprints), Assets (Content)