Skip to content

Commit

Permalink
Remove debug visuals
Browse files Browse the repository at this point in the history
  • Loading branch information
srikavin committed Jan 9, 2020
1 parent 85d493a commit aa350f5
Show file tree
Hide file tree
Showing 4 changed files with 9 additions and 5 deletions.
3 changes: 1 addition & 2 deletions core/src/me/srikavin/fbla/game/FBLAGame.kt
Original file line number Diff line number Diff line change
Expand Up @@ -78,7 +78,6 @@ class FBLAGame : ApplicationAdapter() {

root.setFillParent(true)
root.top().right()
root.debug = true

val gameState = GameState(0)

Expand All @@ -99,7 +98,7 @@ class FBLAGame : ApplicationAdapter() {
DialogueSystem(),
TriggerSystem(listenerManager),
UISystem(),
PhysicsDebugSystem(physicsWorld)
PhysicsDebugSystem(physicsWorld, debug = false)
)
.with(TagManager())
.build()
Expand Down
1 change: 0 additions & 1 deletion core/src/me/srikavin/fbla/game/dialogue/DialogueManager.kt
Original file line number Diff line number Diff line change
Expand Up @@ -62,7 +62,6 @@ class DialogueManager(private val stage: Stage, skin: Skin) {
dialogueRoot = Table(skin)
dialogueRoot.setFillParent(true)
dialogueRoot.center().bottom()
dialogueRoot.debug = true
dialogueRoot.add(dialogueTextContainer)
dialogueRoot.row()
dialogueRoot.add(dialogueOptionsTable)
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -53,7 +53,6 @@ class DropcatchMinigame : Minigame() {
val table = Table(skin).center().bottom()
table.setFillParent(true)

table.debug = true
stage.addActor(table)
itemsLeft = TypingLabel("Items Left: ?", skin)
timeLeft = TypingLabel("Time Left: ?", skin)
Expand Down
9 changes: 8 additions & 1 deletion technical_readme.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,4 +2,11 @@

## Architecture
The game uses [libgdx](https://libgdx.badlogicgames.com/) with Artemis-ODB to facilitate a entity-component-system architecture.
This type of game architecture avoids object-oriented composition within entities--rather, it uses a
This type of game architecture avoids object-oriented composition within entities--rather, it uses a composition-oriented
approach to add behavior to entities. This avoids illogical composition hierarchies while keeping entity behavior
separated from entity data.

Entities only contain data such as position or sprites. Systems operate on groups of entities with specific components. For
example, PhysicsSystem only acts on entities with both components

## Map System

0 comments on commit aa350f5

Please sign in to comment.