View RSS Feed

Minty23185Fresh

A Neophyte Tackles the FG Extension - Change Effect Visibility with One Line (Part 3)

Rate this Entry
Due to posting limits, I have had to split this session into three posts.
This is part 3 of 3.


(continued from part 2)

To test the extension, I deleted all the effects that were applied to the Orc, saved all my edited files, and reloaded the ruleset. Once FG was up I started a second instance of FG and joined the campaign. In the second instance I loaded Zacchaeusís 20th level Paladin and brought up the Combat Tracker. Then I started a third instance of FG, joined the campaign, loaded a 5E character I have on disk, and brought up the Combat Tracker.

In the host, or GM instance, of FG I brought up the Combat Tracker and Effects Manager and then Paralyzed the Orc. Note what does and does not appear in the console for the host session.

Runtime Notice: Host session started
Network Notice: 'Client1' connected
Network Notice: 'Client2' connected
Runtime Notice: s'TWD|manager_effect.lua|addEffect()|status' | s'Arrived in EXT'
The last line shows me that the addEffect( ) function in the extension executed and not the function in the 5E ruleset. The extension overrode the 5E functionality, exactly as desired.

In instance two I used the Paladinís Natureís Wrath to restrain the Orc. The same Runtime Notice appears in the hostís console, again indicating the extensionís code executed rather than the 5E addEffect( ) code.

Following, are three screen shots, one for each instance of FG. In the first screenshot, that of the host instance, note that both effects have an initial visibility of GM instead of VSBL. Also note how the Paralyzed effect is reported in the Chat, with the additional question mark icon, while the Paladinís restrained effect is reported as it usually is.

11a - Host.png

The second screenshot is of the client instance that employís the Paladin. Note that no effects are displayed for the Orc in the Combat Tracker but the restrained effect has been reported as being applied to the Orc in the Chat. A bit paradoxical, but it might be just the behavior I want. I have to think on it!

11b - Client1.png

The second client instance is shown in the third screenshot. Note that none of the effects are shown in the Combat Tracker nor were any of them reported in the Chat. Exactly as desired!

11c - Client2.png

Now for an analysis of my work. Did I accomplish what I set out to do? I think so. But with some caveats. Is the extension ready for release? I think not. For one, I really donít like the idea of having to copy the entire contents of the manager_effect.lua file to my extension. I want to explore alternative solutions to that next time. Also, if I inflict an effect using the Add Effect button on the Combat Tracker, the initial visibility comes up VSBL. The effect is not reported in the Chat nor on either clientís Combat Tracker, so this might be moot, but itís undesired inconsistent behavior. There is some more learning to do and I am really looking forward to it!

Until next time keep on role playing.

Submit "A Neophyte Tackles the FG Extension - Change Effect Visibility with One Line (Part 3)" to Digg Submit "A Neophyte Tackles the FG Extension - Change Effect Visibility with One Line (Part 3)" to del.icio.us Submit "A Neophyte Tackles the FG Extension - Change Effect Visibility with One Line (Part 3)" to StumbleUpon Submit "A Neophyte Tackles the FG Extension - Change Effect Visibility with One Line (Part 3)" to Google Submit "A Neophyte Tackles the FG Extension - Change Effect Visibility with One Line (Part 3)" to Facebook Submit "A Neophyte Tackles the FG Extension - Change Effect Visibility with One Line (Part 3)" to Twitter

Updated June 9th, 2016 at 18:51 by Minty23185Fresh

Categories
Uncategorized

Comments

Log in

Log in