View Full Version : Go Big or Go Gnome
Farratto
March 28th, 2025, 14:56
Go Big or Go Gnome
Current Version: v1.6.0
Updated: 2026-06-04
Adds larger custom sizes to ruleset.
Installation
Install from the Fantasy Grounds Forge (https://forge.fantasygrounds.com/shop/items/2170/view).
You can find the source code at Farratto's GitHub (https://github.com/Farratto/GoBigOrGoGnome).
You can ask questions at the Fantasy Grounds Forum (https://www.fantasygrounds.com/forums/showthread.php?84666).
Details
By using slash commands you can add additional size categories, that will then work seamlessly with the rest of FG as if they had always been there. Once you've added new categories, you'll be able to change those new categories or remove them with more slash commands. This can only be done on the host. This data is stored in the db.xml under "GoBigOrGoGnome.customsizes".
Usage:
Command .................................................. ............................ Description
/listsize .................................................. ................................. lists current size categories
/addsize [name] ([n]) [space] and [reach] .................................... e.g. /addsize colossal (c) 6 and 4
/removesize OR OR [space number] . e.g. /removesize colosal
Notes:
The default for 5E ruleset is that all size categories have a reach of 1. For any custom sizes you add (regardless of ruleset), if you do not specify a reach length, it will default to 1. You can add custom sizes to a 5E ruleset campaign that has a non-1 reach.
I've added some responses for incorrect syntax so hopefully it should be intuitive enough you can figure it out. If you have trouble, ask on the forum (https://www.fantasygrounds.com/forums/showthread.php?84666). I usually respond within a day or two.
Soon, I'll have an export/import function but for now if you want to use your custom sizes on multiple campaigns, either write them down and do them again manually or you can copy/paste the "GoBigOrGoGnome" section of your db.xml.
[size=5]Limitations
You cannot remove or change the ruleset sizes. You can only add larger size categories, not smaller ones.
[size=6]Attribution
The bulk of Go Big or Go Gnome and the last remaining vestiges of Size Matters has been absorbed into the ruleset. What remains is only the slash commands that were wholey written by Farratto.
Icon made by Cathelineau from Game-icons.net (https://game-icons.net/1x1/cathelineau/bad-gnome.html).
SmiteWorks owns rights to code sections copied from their rulesets by permission for Fantasy Grounds community development.
'Fantasy Grounds' is a trademark of SmiteWorks USA, LLC.
'Fantasy Grounds' is Copyright 2004-2021 SmiteWorks USA LLC.
Change Log
v1.6.0: Most of GBoGG was absorbed into ruleset. Removed redundant/interfering code. FIXED: PFRPG2 and 2E rulesets weren't working.
v1.5.2: FIXED: Slash commands were not working.
v1.5.1: FIXED: Errors introduced with last update. Apologies. Expanded other ruleset support.
v1.5.0: FIXED: PFRPG2 ruleset ignoring base size on PCs. Added Ctrl-MouseWheel speed size adjustments and slash commands to some other rulesets. Added protections for erroneous syntax in slash commands.
v1.4.2: FIXED: rare error report misrepresentation.
v1.4.1: FIXED: error in application of new size-system to some rulesets.
v1.4.0: Cosmetic small size option now available to all rulesets. Colossus size added to 4E ruleset. FIXED: Colossus size was erroneously set to 5x5. Now corrected to 6x6. Dot health indicator was not resizing with size changes. Effect tag SIZE: # was adding/removing one grid space instead adding/removing one size category. FEATURE: slash commands to add custom large sizes. Removed previously built-in custom sizes for 5E (other than colossus). Accomodations for ruleset 2026-05-05
v1.3.3: Compatibility update for 2026-05 Ruleset Update
v1.3.2: Compatibility update for FG v4.8.0
v1.3.1: FIXED: some widgets were not using modified sizes
v1.3.0: FEATURE: new size categories of colossal (5x5), giga (6x6), enormous (8x8), epic (10x10), monumental (16x16), cosmic (20x20) for 5E ruleset
v1.2.2: FIXED: typo
v1.2.1: FIX: nil error. Now allows setting reach to none
v1.2.0: REBRANDING of Size Matters. FEATURE: hold ctrl and mouse-wheel up/down to rapidly change size-category of creatures. FIXED: not setting token size correctly for creatures smaller than 1 grid square. FIXED: when adding new token to map that has a size change, that size change was not respected. NEW option to make small creture tokens slightly smaller than medium (aesthetic only).
MrDDT
March 28th, 2025, 20:54
Awesome thank you!
Morenu
March 28th, 2025, 23:31
Thank you for keeping the extensions alive and updating them as well!
Arcanus888
July 17th, 2025, 23:04
Hi, I'm glad I found this extension. Currently setting up a SciFi campaign in 5E, and the ship rules use really big sizes. This extension covers most of them, but would it be possible to add a 50x50 size category? I'm not too bothered by its name. Titanic, Galactic, Planetary, whatever would be easiest for the shorthand.
BlazingAzureCrow
October 11th, 2025, 05:55
Hey Farratto, I'm the author of a series of books behind a setting called Somnus Domina, and part of our system includes some additional huge sizes for mechs, planetary threats, and more - would it be possible to get them added to this extension so they're recognized in 5E? The sizes are
Size - Spaces
Titanic - 10 x 10
Tremendous - 15 x 15
Colossal - 20 x 20
Supermassive - 30 x 30
Planetary - 100 x 100
Superplanetary - 200 x 200
I know there's already a Colossal size in the extension, so might it be possible to perhaps get a setting toggle for the sub-ruleset (our stuff is called 5.19th Edition internally, so maybe a setting toggle to switch between 5E and 5.19E sizes)?
I'd really appreciate this! I'd be happy to pay for your time if needed!
Farratto
October 12th, 2025, 18:27
Hey Farratto, I'm the author of a series of books behind a setting called Somnus Domina, and part of our system includes some additional huge sizes for mechs, planetary threats, and more - would it be possible to get them added to this extension so they're recognized in 5E? The sizes are
Size - Spaces
Titanic - 10 x 10
Tremendous - 15 x 15
Colossal - 20 x 20
Supermassive - 30 x 30
Planetary - 100 x 100
Superplanetary - 200 x 200
I know there's already a Colossal size in the extension, so might it be possible to perhaps get a setting toggle for the sub-ruleset (our stuff is called 5.19th Edition internally, so maybe a setting toggle to switch between 5E and 5.19E sizes)?
I'd really appreciate this! I'd be happy to pay for your time if needed!
I'll take a look.
BlazingAzureCrow
October 12th, 2025, 23:28
Thank you so much! I'd also be happy to comp you our content on DTRPG as part of our thanks for helping!
drempel
October 13th, 2025, 22:55
I asked this on discord for FG and Zacchaeus said I should ask here.
First effect applied:
DE - Brownie Tiny; IF: SIZE(<= tiny); SAVE: 2 dexterity; CHECK: 2 dexterity; DISCHK: strength; DISSAV: strength
This now works as I expect, if the creature is tiny they get a +2 and the disadv applied.
now, if I apply
DE - Brownie Enlarged; SIZE: (small)
The SAVE and CHECK bonuses are no longer applied as expected, but the disadvantages still are.
I was expecting them to not be anymore, like the SAVE and CHECK
(I'm preparing for a playtest of a new lineage/species I made for my upcoming tales of the valiant/5e module
Zacchaeus then responded with: I don’t have an answer. You’d need to ask the extension developer how their extension interacts with effects
Anyone know why the SAVE: and CHECK: get disabled but the DISSAV: and DISCHK: don't?
edit: answered on discord. "SIZE: small" works. Weird that SIZE: (small) half worked but I'm happy.
Seleh
January 23rd, 2026, 17:47
My 3.5e heart thanks you for bringing colossal back into 5e :) Now a greatwyrm can truly be represent its 3.5 size, though Fizban's still calls it gargantuan. We all know they are colossal.
BlazingAzureCrow
January 23rd, 2026, 17:49
Heya! I was just wondering if you ever had time to consider this?
Farratto
January 24th, 2026, 21:52
Heya! I was just wondering if you ever had time to consider this?
I did yes. Sorry for not keeping you in the loop. The problem is that I have several people asking for different size categories. So I'm going to add a window that allows you to add custom size categories. It's in the works but might be some time still. I am very busy at work right now, so crosses fingers maybe the next few weeks, maybe next few months.
BlazingAzureCrow
January 24th, 2026, 21:59
I'm just happy to hear it's in the works! Good luck~!
Farratto
May 7th, 2026, 13:26
So I decided to implement the custom sizes when I was updating for the new patch. I also fixed some bugs I found as I was working. This is a significant patch. Here are the release notes:
75% small size option now for all rulesets
Colossus size added to 4E
FIXED: Colossus size was erroneously set to 5x5. Now corrected to 6x6.
FIXED: Dot health indicator was not resizing with size changes
FIXED: Effect tag SIZE: # was adding/removing one grid space instead adding/removing one size category
FEATURE: slash commands to add custom large sizes. Removed previously built-in custom sizes for 5E (other than colossus)
Accomodations for ruleset 2026-04-28
Please see the readme included in the extension or the orginal post of this forum for instructions on how to use the new slash commands. If you can't get it to work, respond to this post.
Nyarly Dude
May 7th, 2026, 23:27
I see an error in the logs for a test PF2RPG campaign with no other extensions loaded.
[5/7/2026 3:25:59 PM] [WARNING] windowclass: Window class (npc_combat_summary_fields) defined with merge attribute, but asset name does not match existing asset. [GoBigOrGoGnome] [campaign/record_creature.xml]
[5/7/2026 3:25:59 PM] [WARNING] windowclass: Window class (charsheet_notes_details) defined with merge attribute, but asset name does not match existing asset. [GoBigOrGoGnome] [campaign/record_creature.xml]
[5/7/2026 3:25:59 PM] [WARNING] windowclass: Window class (vehicle_combat_standard) defined with merge attribute, but asset name does not match existing asset. [GoBigOrGoGnome] [campaign/record_creature.xml]
[5/7/2026 3:25:59 PM] MEASURE: EXTENSIONS LOAD - 0.003557 - 1
[5/7/2026 3:26:03 PM] MEASURE: MODULE LIST BUILD - 3.5075421 - 108
[5/7/2026 3:26:03 PM] MEASURE: REFRESH IMAGE ASSETS - 0.0431998
[5/7/2026 3:26:03 PM] MEASURE: REFRESH PORTRAIT ASSETS - 0.0305189
[5/7/2026 3:26:03 PM] MEASURE: REFRESH TOKEN ASSETS - 0.0488526
[5/7/2026 3:26:03 PM] MEASURE: ASSET LIST BUILD - 0.1245713
[5/7/2026 3:26:04 PM] MEASURE: LOAD - PART 1 - 19.843736
[5/7/2026 3:26:06 PM] [ERROR] Script execution error: [string "GoBigOrGoGnome:scripts/manager_size.lua"]:885: attempt to perform arithmetic on local 'nSpace' (a nil value)
[5/7/2026 3:26:07 PM] MEASURE: MODULE LOAD - 0.0793126 - GM Core - Pathfinder 2 ORC
[5/7/2026 3:26:07 PM] MEASURE: MODULE LOAD - 0.4009389 - Monster Core - Pathfinder 2 ORC
[5/7/2026 3:26:07 PM] MEASURE: MODULE LOAD - 0.2594596 - Player Core - Pathfinder 2 ORC
[5/7/2026 3:26:08 PM] MEASURE: MODULE LOAD - 0.5215827 - Player Core 2 - Pathfinder 2 ORC
[5/7/2026 3:26:09 PM] Fantasy Grounds - v5.1.8 (2026-04-14)
Farratto
May 8th, 2026, 12:18
I see an error in the logs for a test PF2RPG campaign with no other extensions loaded.
I don't see any errors here. Are you talking about the warnings? Please ignore warnings. They don't indicate a failure of function.
estrolof
May 8th, 2026, 12:30
I see the error in the log, it's hard not to miss it.
[5/7/2026 3:26:06 PM] [ERROR] Script execution error: [string "GoBigOrGoGnome:scripts/manager_size.lua"]:885: attempt to perform arithmetic on local 'nSpace' (a nil value)
Farratto
May 8th, 2026, 13:34
And there it is. My apologies. Looks like my changes aren't working for PFRGP2. I'll take a look. It was working on this ruleset before, right?
Farratto
May 8th, 2026, 14:15
Nevermind. I found and fixed my error. It should be working on all rulesets now. Please let me know if you find anything else.
Zaister
May 12th, 2026, 10:52
It seems with the newest updates, this extension no longer allows my Large PCs to be large in my Pathfinder 23E campaigns. Can you check perhaps what's causing this?
Farratto
May 12th, 2026, 14:25
It seems with the newest updates, this extension no longer allows my Large PCs to be large in my Pathfinder 23E campaigns. Can you check perhaps what's causing this?
I took a look at it's behaving in the same way with the new version as it was with the old version. But I really only play 5E so I'm probably just not testing it correctly.
Can you give me more details?
In what way are you attempting to make the PCs large?
You are using the Pathfinder 2E ruleset?
Any errors or it just doesn't work?
Zaister
May 12th, 2026, 17:09
Certainly. I'm playing with the Pathfinder 2E ruleset, and I have a minotaur PC in my party. Size Large is applied through the character's ancestry (race). That has always resulted in the character taking up 4 spaces and a larger token, as would be expected.
Now, with the latest FG and ruleset updates, the character is now displayed as Medium size, taking just 1 space and normal token size. Changing the character's space via the combat tracker does nothing (previously it would have adjusted the character's space on the map that is colored on green. Delelting the token and re-adding it to the map does not change this behavior,
This happens only with this extension active. When I disable it, the character loads as normal.
vonBlashyrkh
May 13th, 2026, 13:17
Hello, for me it's having a similar effect. Also in Pathfinder 2E.
I can make an effect, say for Enlarge and apply it and it works just fine, a medium creatures token space and reach change to the appropriate size, and they return to medium after the effect ends.
However any creature listed with a base size larger than medium (large / huge / whatever) when added to the combat tracker also becomes medium. I can add the effect text from the extension and they'll change to whatever size I give them. But the default size for every creature with the extension active seems to be Medium.
I can also confirm with the extension disabled this does not happen, and all creatures begin with their correct size.
Farratto
May 13th, 2026, 16:37
I'm sorry. The NPCs are appearing as their correct size for me for both with the extension loaded and with it unloaded (without an effect). Large PC I am unable to test because I don't have a large race in the free version of PFRPG2. I did try changing the size in the character sheet but that does nothing without the extension as well.
There's nothing I can do if I can't recreate the problem. Can one of you zip up your campaign and send it to me (you can leave out the images to save space)?
Maybe you all are using a different ruleset, different map, language, version of FG, version of GBoGG or some other extension is interfering?
Farratto
May 16th, 2026, 01:49
I didn't receive any additional information from anyone so I did some digging on my free time this week. Still, the PFRPG2 ruleset was working perfectly for NPCs both with and without GBoGG loaded so I don't know what's happening to the two of you there.
Though I DID find a problem with PC sizes, but it had nothing to do with GBoGG. It was a problem with the PFRPG2 ruleset, which was happening both with GBoGG loaded and without GBoGG loaded. I don't know if this is the same problem you all are having or not. But weirdly, after going back to look at older versions of the PFRPG2 ruleset, I can't see any reason why this would start happening now.
In any case, I produced a fix for the problem I did find (and added a couple features to the PFRPG2 ruleset while I had the hood open). I'm gonna test it a little more before I upload it to the forge. But hopefully this fixes your problems. You should see an update in the next few days. Let me know how it goes for you.
Farratto
May 18th, 2026, 01:41
It's been upped now. Let me know how it goes.
SilverDarkCureXZ
May 18th, 2026, 06:14
Whenever you go into the character notes tab and adjust the window size, the console gives an anchoring error.
[5/18/2026 12:13:28 AM] Fantasy Grounds - v5.1.9 (2026-05-15)
[5/18/2026 12:13:28 AM] RULESET: Dungeons and Dragons (5E) ruleset (2026-05-05)
Copyright 2026 Smiteworks USA, LLC
[5/18/2026 12:13:28 AM] RULESET: Core RPG ruleset (2026-05-05)
Copyright 2026 Smiteworks USA, LLC
[5/18/2026 12:13:28 AM] EXTENSION: Go Big or Go Gnome v1.5.0 by MeAndUnique and maintained by Farratto.
[5/18/2026 12:13:28 AM] MEASURE: LOAD - PART 2 - 12.810549
[5/18/2026 12:13:40 AM] [ERROR] window: No vertical anchor defined for control (size) in windowclass (charsheet_notes)
[5/18/2026 12:13:40 AM] [ERROR] window: No vertical anchor defined for control (size) in windowclass (charsheet_notes)
[5/18/2026 12:13:40 AM] [ERROR] window: No vertical anchor defined for control (size) in windowclass (charsheet_notes)
Shadeside
May 18th, 2026, 06:38
To elaborate on the above post, the same type of error shoots off twice whenever the size field is updated in my own testing in the 5e ruleset.
Farratto
May 18th, 2026, 14:50
My bad. It should be fixed now. Thank you for reporting.
jkeller
May 20th, 2026, 20:02
Hey! I'm getting a very weird conflict with my (not yet released) SpellFX extension:
[ERROR] Script execution error: [string "GoBigOrGoGnome:scripts/manager_size.lua"]:41: stack overflow
It happens when I call: Image.addLayer(nodeMap, "image", tData, 1);
UPDATE:
Working now, thanks for the help!
wardrake
May 25th, 2026, 11:45
Does the extension change the damage output scaling for size categories in Pathfinder and 3.5? When I apply size in the latest version it changes the token size and reach but doesn't affect the damage of weapons - is that correct?
Farratto
May 25th, 2026, 12:04
Does the extension change the damage output scaling for size categories in Pathfinder and 3.5? When I apply size in the latest version it changes the token size and reach but doesn't affect the damage of weapons - is that correct?
That is correct. This extension is only for sizing, really. If you want to change the size of the token AND change damage. You're going to want to use some effect tags. You can also change the size of the token with an affect tag as well.
As an example, in 5e there is a spell called enlarge/reduce. You can do "Enlarge; DMG: 1d4; SIZE: 1". This effect will increase the damage of the creature by 1d4 and the size of the token by 1 size category. You can also use negatives for reducing.
Tantrum
May 25th, 2026, 14:59
There was a extension that changed the damage for Pathfinder / 3.5e but its not currently working because it's creator is no longer active in Fantasy Grounds.
In pathfinder / 3.5e changing size does change the actual damage dice of the weapon/attack, so that's not possible to do with general Effects.
Farratto
May 25th, 2026, 15:18
There was a extension that changed the damage for Pathfinder / 3.5e but its not currently working because it's creator is no longer active in Fantasy Grounds.
In pathfinder / 3.5e changing size does change the actual damage dice of the weapon/attack, so that's not possible to do with general Effects.
That sucks that the author is no longer active. Unfortunately, I don't want to get involved supporting rules that are specific to a ruleset I don't play. That's why we have effect tags, so you can achieve things that are not universal.
I don't know why you're saying it's not possible with effects. I literally just told you how to do it with effects, and gave an example.
jimlad42
May 25th, 2026, 16:15
I believe in Pathfinder/3.5, it's not additional damage, but changing the damage die. Like, a Medium creature's bite does 1d6, while a Large creature's bite does 1d8. And that's not an effect that can be done with standard effects. I might be wrong, though, it's also not my system.
Farratto
May 25th, 2026, 17:23
I believe in Pathfinder/3.5, it's not additional damage, but changing the damage die. Like, a Medium creature's bite does 1d6, while a Large creature's bite does 1d8. And that's not an effect that can be done with standard effects. I might be wrong, though, it's also not my system.
Ah, okay. That would explain it. That does sound hard or impossible to do with current effect tags.
If you can tell me what extension it was and I can get ahold of the source code and it doesn't look like too much work, I may absorb it's functionality into GBoGG.
Tantrum
May 25th, 2026, 17:40
It's the "3.5E & Pathfinder Size Changes" by SoxMax. There's a forum thread of it with reports of errors here (https://www.fantasygrounds.com/forums/showthread.php?71978-3-5E-PFRPG-Size-Changes).
And this is the Forge page (https://forge.fantasygrounds.com/shop/items/437/view)
Farratto
May 25th, 2026, 18:20
It's the "3.5E & Pathfinder Size Changes" by SoxMax. There's a forum thread of it with reports of errors here (https://www.fantasygrounds.com/forums/showthread.php?71978-3-5E-PFRPG-Size-Changes).
And this is the Forge page (https://forge.fantasygrounds.com/shop/items/437/view)
Thanks for the link. I'll take a look
Shadeside
May 25th, 2026, 18:34
I noticed today that the command to add new sizes isn't working properly. Whenever I type it in the command correctly (even using the example it gives me), it shoots out the "syntax for adding" text and doesn't add the size. I know these commands and the syntax were working a few weeks ago, when the big effect update released.
Farratto
May 26th, 2026, 13:57
I noticed today that the command to add new sizes isn't working properly. Whenever I type it in the command correctly (even using the example it gives me), it shoots out the "syntax for adding" text and doesn't add the size. I know these commands and the syntax were working a few weeks ago, when the big effect update released.
Thanks for reporting. It should be fixed now.
Moon Wizard
June 4th, 2026, 01:45
Just pushed a CoreRPG update which implements all the features using the built-in ruleset data (does not support any custom data overrides; though Colossal sizes were added to 2E, 4E, 5E).
You should probably disable this extension until Farratto gets to take a look.
Regards,
JPG
Farratto
June 4th, 2026, 18:41
Most of what Go Big or Go Gnome was doing was absorbed into the rulesets. I've taken all the extreaneous and interfering code out.
The only thing Go Big or Go Gnome is doing now is providing the ability to add additional larger sizes to your ruleset. If you are not using this feature, you can stop loading Go Big or Go Gnome. If you are using this feature. Just do nothing, and everything should continue to work as expected.
Please let me know if you have any troubles.
BlazingAzureCrow
June 16th, 2026, 05:39
Is the Colossal size baked into the 5E ruleset itself currently? Our table uses a different size spacing for Colossal and we'd like to be able to change it if we could.
Moon Wizard
June 16th, 2026, 05:41
Yes, Colossal is baked into all the D&D and Pathfinder/Starfinder rulesets now, even if not official to the systems.
Regards,
JPG
Farratto
June 16th, 2026, 12:25
Is the Colossal size baked into the 5E ruleset itself currently? Our table uses a different size spacing for Colossal and we'd like to be able to change it if we could.
Being able to change the baked-in rulesets requires a bit of different code, which is not currently present. It's not something I can just quickly throw in. The original intention was not to give complete freedom over the sizes, but I was getting so many different requests for different larger sizes, I decided to implement the custom larger sizing system. It wouldn't be a complete rewrite to make all the sizes customizable, but it also wouldn't be a quickie. I will add it to my "todo" list, but I can't make any promises as to when it will happen.
Powered by vBulletin® Version 4.2.1 Copyright © 2026 vBulletin Solutions, Inc. All rights reserved.