Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

Strive: Conquest

A successor to first Strive For Power game, currently at alpha stage · By Strive4Power

0.11.0b Resurrect spell not working, Burn status... sometimes

A topic by Jotok created May 18, 2025 Views: 260 Replies: 2
Viewing posts 1 to 3
(+1)

Zephyra tried to Resurrect Kurdan during a fight:

SCRIPT ERROR: Invalid get index 'a_res' (on base: 'Dictionary').

          at: atomic_effect._init (res://src/classes/atomic_effect.gd:10)

SCRIPT ERROR: Invalid get index 'type' (on base: 'Dictionary').

          at: apply_atomic (res://src/character/CharacterClass.gd:1664)


Kurdan remained dead.  A second attempt at the spell had the same result.


During a fight with Fire Bombs thrown by my side and an enemy mage throwing Fire Bolts:

SCRIPT ERROR: Invalid get index 'burn_new' (on base: 'Dictionary').

          at: triggered_effect.e_apply (res://src/classes/triggered_effect.gd:108)

SCRIPT ERROR: Invalid get index 'burn_new' (on base: 'Dictionary').

          at: triggered_effect.e_apply (res://src/classes/triggered_effect.gd:108)

SCRIPT ERROR: Invalid get index 'burn_new' (on base: 'Dictionary').

          at: triggered_effect.e_apply (res://src/classes/triggered_effect.gd:108)

SCRIPT ERROR: Invalid get index 'scriptedevents' (on base: 'Dictionary').

          at: check_events (res://src/core/globals.gd:1264)

SCRIPT ERROR: Invalid get index 'burn_new' (on base: 'Dictionary').

          at: triggered_effect.e_apply (res://src/classes/triggered_effect.gd:108)

SCRIPT ERROR: Invalid get index 'burn_new' (on base: 'Dictionary').

          at: triggered_effect.e_apply (res://src/classes/triggered_effect.gd:108)


No one had burn status applied.  At other times, the Fire Bomb was used, but there was no error message and no burn status applied.  Another time burn status *did* appear, when a Warlock in a Bandit Fort used Incinerate.

Resurrect still doesn't work in 0.11.0c, same error.  I saw an NPC apply burn status from a firebolt to one of my characters, though.

should be fixed now