-
June 13th, 2020, 19:06 #971
- Join Date
- Jul 2018
- Posts
- 78
Yep, it is incorrect. Zacchaeus is right.
The extension puts it on the layer you are currently one when you build the encounter. So if you are using official stuff, it is base layer, which is a pain in the butt. When you BUILD yours, however, put that pin on the top and make sure you are on that layer when dropping them in from the encounter, and it will put them on the top.
-
June 13th, 2020, 20:32 #972
-
June 13th, 2020, 21:55 #973
The poster I was responding to said, "Using preset adventures (hoard of dragon queen actually)". Hence he will experience what Scried said.
Fantasy Grounds Unity Lives! Good job, Smiteworks!
-
June 14th, 2020, 08:57 #974
- Join Date
- Mar 2020
- Posts
- 5
Managing with extension I found that Death Indicators is causing conflict with Combat Enhancer, CE is working properly. I will remove DI to make it working correctly.
-
June 20th, 2020, 02:43 #975
- Join Date
- Oct 2018
- Posts
- 5
Is there an easy(ish) way to just disable the feature where PC's reduced to 0 HP "fall" to the middle layer? It becomes a chore when party members want to drag a fallen ally to safety if they don't have healing readily available, and finding the PC on the combat tracker to administer healing when they are more accustomed to interacting with tokens is sometimes difficult as well.
I love some of the options that the layers add, and really like the elevation feature, but a little more modularity on what's active and what is disabled would be nice.
-
June 23rd, 2020, 12:29 #976
I'm new to FG and just trying to work out how this would benefit me, but I guess the most important question for me (sorry if it's obvious) is does this work with FGU?
-
June 23rd, 2020, 13:22 #977
There is a different version for Unity. It's in this thread: https://www.fantasygrounds.com/forum...53-5E-Enhancer
Also, a good rule of thumb on extensions is if you don't know what it does and how it'll help, don't use it. Any extension has a chance to conflict with others. So don't use more than you need. Especially ones that deal with combat.Fantasy Grounds Unity Lives! Good job, Smiteworks!
-
June 23rd, 2020, 13:46 #978
-
June 25th, 2020, 18:37 #979
- Join Date
- Dec 2017
- Posts
- 2
The Spells Produce Flame and Radiant Sun Bolt no longer work. Next to the target, 10 ft, 15 ft, 30 ft, 40 ft. Flying in the air. This is the only result that you get.
Script Error: [string "scripts/ranged_attacks.lua"]:40: attempt to concatenate local 'maxRange' (a nil value)
-
July 3rd, 2020, 08:58 #980
- Join Date
- Apr 2018
- Posts
- 6
Grab the latest ranged_attacks.lua from the scripts folder on GitHub (it's not updated in the in the INSTALL VERSIONS folder), it looks to have this issue fixed. Alternatively, you can do what I did and edit the file; within the if block on lines 413-449, move the "Spell Action version 1" block to before the "Weapon version 1" block.
The result ends up looking something like this:
Code:-- Spell action version 1 -- this exception is needed as some modules have a slightly different range entries -- where spell entries on NPCs are put under actions, and only one range is available -- string input ex. 'Ranged Spell Attack: +5 to hit, range 150 ft., one target. Hit: 10 (3d6) fire damage. ...' rangeText = string.match(description, "ranged?%s%d+"); if rangeText ~= nil then medRange = string.sub(rangeText, 7, string.len(rangeText)); maxRange = medRange; end -- Weapon version 1 -- search for 'range * ft', return range as substring, split substring in two (medium/max range) -- string input ex. 'Thrown (range 30/120)'' and 'range 30/120 ft.'' rangeText = string.match(description, "ranged?%s%d+/%d+"); if rangeText ~= nil then -- find '/' index -- medRange = start of numbers to before index -- maxRange = after index to end local index = string.find(rangeText, '/'); medRange = string.sub(rangeText, 7, index - 1); maxRange = string.sub(rangeText, index + 1, string.len(rangeText)); end -- Weapon version 2 -- this exception is needed as some modules have a slightly different range entries -- string input ex. 'Thrown (range 30 ft./120)'' and 'range 30 ft./120 ft.'' rangeText = string.match(description, "ranged?%s%d+%s?[a-zA-Z]+\.?/%d+"); if rangeText ~= nil then local index = string.find(rangeText, '/'); medRange = string.match(string.sub(rangeText, 7, index), "%d+"); maxRange = string.sub(rangeText, index + 1, string.len(rangeText)); end
ranged 150/600 (ranged instead of range)
range 150ft./600 (no space between 150 and ft.)
range 150 ft/600 (no period in ft.)
range 150 m/600 (any unit of any character length)
Open up ranged_attacks.lua from Token Helper. Go to around line 516 and change:
local rangeText = string.match(description, "%d*");
to:
local rangeText = string.match(description, "%d+");
Then just edit the spell in FG (may need to add it to the character's sheet first), and add the range. For Produce Flame I've got Self, 30ft; Radiant Sun Bolt is the same just without Self. The code change for this part ensures that it won't match an empty string and get a range of "" from "Self, 30"
This gets me the correct output of "The ranged attack is OUT OF RANGE and misses. Produce Flame (30) from 540 feet."Last edited by AliAthena; July 3rd, 2020 at 23:54. Reason: minor formatting
Thread Information
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)
Bookmarks