Skip to content

Conversation

Rusty-Box
Copy link
Member

This PR only containts WIP still frames for each considered Ghost Tree action to provide visuals for coding in the planned, new behavior of said Ghost Tree!

List of actions as of now:

  • idle (normal + pinch)
  • scream (normal + pinch)
  • charge (normal + pinch)
  • busted

Explainiation of planned behavior change (for coders):
The Ghost Tree will start begin the battle with a scream, spawning wisps that DO NOT hurt Tux. After which it will suck in the wisps (use scream action for now) and initiate the proper color-coated attacks with another scream. During all this the Main Root Attack is instigated on occasion, behaving essentially like a Root Sapling root attack.

During full health (5 HP) the Ghost tree only makes use of the Red Root Attack. During 4 HP, the Green Root Attack. 3 HP, the Blue Root Attack etc. When all colored attacks are completed, the Ghost Tree will go into its recharge action revealing its core. That core Tux can jump on to land a hit on the Ghost Tree, after which the Ghost Tree hides its core again.

Pinch Mode:
During Pinch Mode the Ghost Tree will loose it's branches, do a scream, spawn all 3 colors of wisps and swallow them -> do another scream and initiate the Pinch Root Attack multiple times.


Red Root Attack:

  • A wave of red glowing roots will emerge from the ground, (from the side furthest from Tux's position relative to the Ghost Tree) going from one end to the other.

Green Root Attack:

  • Spawn a green glowing Root at Tux's latest position which hurt Tux on touch as well as explodes when touched or after a few seconds, bursting into smaller Root Spikes that break upon touching the ground.

Blue Root Attack:

  • Spawns a "Granito" Root at Tux's latest position that after reaching max height, shoots one blue glowing Root Dart out of each Granito head before retracting back into the ground (there's two variants - those can be randomized)

Pinch Root Attack:

  • Combines aspects of all attacks. A Pinch Root will spawn at Tux's latest position out of which a wave of red glowing roots emerge on both sides, shoot a blue glowing Root Dart on both sides and the Root itself explodes into Root Darts soon after.

The following videos show a scripted example of each Root Attack:

ghosttree_wip_attack_concepts_scripted.mp4
ghosttree_wip_pinchattack_concept.mp4

@Rusty-Box Rusty-Box added type:feature category:code category:design status:needs-work In progress, but no one is currently working on it (New volunteers welcome) labels Mar 20, 2025
@Rusty-Box Rusty-Box added this to the 0.7.0 milestone Mar 20, 2025
@rttyg46305Unj
Copy link

make it more like the worldmap

@korbanpapa
Copy link

actually they're probably going to redo the worldmap sprite for the ghosttree

@rttyg46305Unj
Copy link

yeah ok
thats sad for me

@rttyg46305Unj
Copy link

and i don't want it looking like a dog

@Hypernoot
Copy link
Member

superseeded by #3334

@Hypernoot Hypernoot closed this Sep 7, 2025
@Frostwithasideofsalt
Copy link
Member

seems mostly fine, my only real complains are that the attacks seem slow and are on a oddly high z layer, the hitbox for the orb is slightly too high, and i feel like the ghost tree should open his mount only when inhaling wisps- also i dont really undestand when it's face sorta comes off? it feels kinda random.

@Frostwithasideofsalt
Copy link
Member

also just to mention it before someone else does, it feels really unpolished rn, but that doesnt matter because its very blatantly unfinished and its just important to get the basic behavior down first, and the visual polishing with stuff like particle animations can just be done later or in another pr. So yeah little johnny dont be commenting "why is the ghost tree so bad,,,... or whatever" lol

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
category:code category:design status:needs-work In progress, but no one is currently working on it (New volunteers welcome) type:feature
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants