PDA

View Full Version : Incorrect cone size and shape



spite
May 8th, 2016, 09:37
So I was wondering, is there any way to make the cone work as per the 5th edition rules? The PHB states that a cone's width at a given point along its length is equal to that point's distance from the point of origin. This results in a 53 degree cone, unlike the 90 degree cone that the 5th edition ruleset uses.
We should have something like https://puu.sh/oKjvS/65cf027aa5.png that, instead of something like https://puu.sh/oKjxy/9ef95533ba.jpg that. The second only works if you use a variant rule for diagonal distance (where the second diagonal is 10' alternating.)

Zacchaeus
May 8th, 2016, 11:28
Some discussion on this subject here (https://www.fantasygrounds.com/forums/archive/index.php/t-27905.html).

spite
May 8th, 2016, 20:53
Thanks Zacch, looks like its just a waiting game, or a game of learning to code ><

ffujita
May 10th, 2016, 02:56
So *that* is why the dragon turtle in PotA was so difficult to kill. (with a 65' cone steam breath weapon)

Athlonis
September 12th, 2016, 23:59
has anyone managed to create a fix for the cone issue? or instructions that a non-programmer can understand? I'm a bit confused trying to read the wiki article about custom pointers since it refers to CoreRPG which im not sure is what's used for 5e and which files to edit.

Zacchaeus
September 13th, 2016, 00:06
It has been fixed in the next version of FG which should be released soon. CORE is a rule set on which many other rule sets are based including 5e.

JohnD
September 13th, 2016, 01:13
So *that* is why the dragon turtle in PotA was so difficult to kill. (with a 65' cone steam breath weapon)

Don't give away DM trade secrets.

rob2e
September 13th, 2016, 08:54
65' cone of steam. Used it. Killed a party and a half.

Athlonis
September 13th, 2016, 20:09
It has been fixed in the next version of FG which should be released soon. CORE is a rule set on which many other rule sets are based including 5e.

cool. thanks for the info.

Brynnan
September 14th, 2016, 04:14
*Soon

peterfdh
August 5th, 2020, 22:49
*Soon

Was this ever fixed?

Zacchaeus
August 5th, 2020, 22:51
Was this ever fixed?

According to post #6 above it was in 2016.