Advanced Search
Search Results
32 total results found
Auras
Auras are temporary or permanent effects on a unit. They can be DoTs, HoTs, buffs, debuffs or absorbs. Every unit has an aura_container scene, which has a Node type root node, and contains Node type nodes named dot_container, hot_container, buff_container, deb...
Entering the Combat Script
There are a number of functions that are intended as entrypoints into the combat script, which are called by spell scripts. The appropriate function must be called to properly proceed through a combat event. combat_event_entrypointThis function serves as the ...
Combat Events
Combat events are damage, healing and aura events that are reached via the entrypoints into the combat script. They calculate the magnitude of a spell, unless prescribed, check for avoidance and ciritcal hits, apply the hp change or aura to the target, and log...
Checks
There are a few checks that the combat script requires to function. is_criticalThis function checks whether a hit is critical. It uses the crit modifier of a spell and the base critical hit chance of the source as arguments. A random number generator is initi...
Value Application
The final part of the combat event sequence, before the logging, is the application of the final spell value to the absorb shields and health of the target. apply_damageThis function applies damage to the health of the target, and returns the difference betwe...
Stat Modificiation
Stat modification occurs when a buff or debuff is applied to a target, and an array of stats is changes either additively (positive or negative) or multiplicatively (with values greater than or less than 1). apply_buffThis function applies the stat modificati...
Log Messages
All combat events are logged, to ensure that combat encounters can be analyzed. No in-game analysis exists currently, but is planned to be implemented at some point. It is not actively being developed at the moment, however. In the future, it is intended that...
Actionbars
Actionbars are grid containers that contain buttons. Spells can be assigned to the buttons, which allows clicking or using the appropriate hotkey to trigger the spell. LayoutBy default, there are two actionbars with 12 slots each. The number of columns is s...
Links
Fall of the House of Usher - Overview Class Design Technical Documentation
Tasks
The following tasks would be reasonable to tackle: Lore Rough concept for class designs of non-Agatha characters More detailed concept for Agatha Adaptation of the short story to the playable map Maps Hub map layout Pipeline from Blender...
Spell Queue
In order to make spell casting smoother, and not have short gaps between spells when the next is not triggered frame-perfectly, a spell queuing system exists. This system allows spells to be queued towards the end of a currently active cast, or a currently act...
First Playable Alpha
The first playable alpha should consist of a functioning hub map, the first playable map (The Fall of the House of Usher), and at least one class per role that can be played. A more detailed list of features is as follows: A list of required features(cheese...
Overview
The Fall of the House of Usher is a short story written by Edgar Allan Poe. It is adapted to fit the meta narrative of RadGame, and serves as the thematic map for Agatha, the Void Girl. Lethebron, the God of Being Forgotten, and Necria, the God of Being Rememb...
Boss 1
The Pontifex The Pontifex attempts to establish a tether between the realm of the dead and the realm of the living. The players can choose how strong the connection between the two realms is, which sets the difficulty for the rest of the map. To truly banish t...