Printable View
Exporting has been mentioned earlier in this thread, but development of that has been put on hold (see post #24).Quote:
Originally Posted by JamesBlackwing
If you're familiar with XML (or want to learn on the fly) you may be able to manually copy the Shop & Town info from the campaign db.xml file into a module - look how story entries etc. are stored in a module xml compared to the db.xml of the campaign and see if you can create a module yourself! :)
Drop a request to bradmcadam who developed the Shop/Town extensions and request that he register the pertinent database nodes with the /export utility. This will then allow you to be able to export Shop/Town Information to modules.Quote:
Originally Posted by JamesBlackwing
How difficult (time to design) is it to do that, Dr.Z?Quote:
Originally Posted by DrZeuss
Very simple, for 3.5E/4E just add the following in an onInit() function:Quote:
Originally Posted by bnason
Where:Code:if ExportManager.registerExportNode then
ExportManager.registerExportNode({ name = <db root node>, class = <windowclass>, label = <label>});
end
<db root node> is a string of the database node (under root) to export
<windowclass> is a string defining the name of the window class
<label> is a string defining the label to use for the new entry in the /export window
e.g.
would add a Table entry to /export which will export nodes under table (under root) of class table.Code:if ExportManager.registerExportNode then
ExportManager.registerExportNode({ name = "table", class = "table", label = 'Table"});
end
Okay! So here's 1.6:
I'd like to give a huge thanks to DrZeuss, Griogre, Silveras, and Trenloe for helping me put my thoughts together and get the code needed to complete the features on the to do list. If you feel you contributed and I missed your name, I apologize, you are also awesome. :)
Changelog:
- Changed naming convention so now you simply replace the old files and they'll overwrite. No more having 15 copies of my silly addon
- Added chat window output so you can see the version # you're using as it loads up in case you forgot to look at the version # in the display window where it is also visible
- Added the ability to export towns & shops. I have only tested this a little, so please do some thorough testing of it yourself and report bugs to me.
Enjoy!
Happy to see this, and I will give the export some testing just about immediately.
Were you able to resolve the issue you were having with the drag-n-drop in the lists creating new nodes instead of linking to the existing ones?
Unfortunately I haven't had a lot of time to spend on the addon, so no I wasn't. I have a feeling it'll take me a lot more scripting to get the exact functionality I want out of it. I do apologize for that.
No need to apologize... I appreciate the efforts and find the extension quite useful "as-is".
The exporting worked nicely for me tonight, no problems at all using the exported module with my main campaign.
A couple of thoughts
- I am not sure how many towns you expect to see listed together. For my own use, I will probably create a module for each city or town, so the town list window will be mostly empty, usually one entry.
- Have you considered a tab for Districts? The new Magnimar supplement breaks each district out separately, allowing each to have different modifiers and lists of places of interest.
- For the shops... had you considered giving them a "type" field ? I noticed that the new Magnimar supplement breaks out the interesting sites in each District by broad categories like "Entertainment" and such. I think you had said you wanted the NPC list to be sortable by either the name or job column? If so, a similar list for sites, sortable by name or type (or, more ambitiously, name/type/district), would be a nice addition.
In any event, the extension is very helpful and effective right now, so thanks for the effort and for sharing.
Once I figure out the sorting I'll make sure it can sort by each column. I'll look into dividing it into districts. I'm weary of having more subwindows each time, although there could still be a nice way to arrange it.
As for how many towns are listed together. I have some pretty nutty players. The scroll box for tabs allows for added tabs at the bottom, each with labels, and my players are currently jumping between 25 towns in a country roughly the size of France, each tab for me keeps track of a different country. Most of my design for this addon has been to try and stay one step ahead of their crazy brains. The rest is things you all request, so the more data you give me like the districts idea, the better I can make it :)
As for the shops idea, that was really quickly thrown together. I'm thinking about changing it to a 'businesses' or 'establishments' addon with a 'goods and services' tab for trading items, but I agree, it needs more info in general for taverns, inns, 'companion' type shops (woo! firefly reference) etc. I'll jot some ideas this week.
Dumb question - I have a custom theme that I use, and I've tried modifying the Town/Shop buttons in the theme file like this:
in my graphics_misc.xml. Every other button from the default 3.5e theme that I've reskinned shows up correctly - but this doesn't appear to work with the extension.Code:<icon name="button_towns" file="graphics/sidebar/button_towns.png" />
<icon name="button_towns_down" file="graphics/sidebar/button_towns_down.png" />
<icon name="button_shops" file="graphics/sidebar/button_shops.png" />
<icon name="button_shops_down" file="graphics/sidebar/button_shops_down.png" />
Is there some other way that I can call for the icon name to be reskinned from the Town/Shop extensions? I'm assuming that the lines in my theme/extension XML are being called BEFORE the actual town/shop extension, and therefore overridden, or something like that.
Of course - I can always just manually replace the PNGs in the extensions, but that's a PITA :)
bnason - How do you change the icons in 3.5e, is it by editing the ruleset (your graphics_misc.xml file you mentioned) or some other means? If you edit your ruleset directly I'm pretty sure you would have to edit the extensions as well. I'll look into what I can do to have them pull from non-extension resources but I did make it a point to keep them self-contained and independent of the ruleset. Sorry this bug arose as a result.
The way theme extensions work is pretty simple - the base extension.xml calls a set of XML files that redefine the ruleset interface, for example:
That in turn contains a set of (definitions?) that complement/replace the base ruleset. For example, in the 3.5 ruleset, the default graphics_misc.xml (it's in the 3.5E.pak ruleset in the default Fantasy Grounds II install location - program files, not the appdata directory), you have:Code:<includefile source="graphics/graphics_frames.xml" />
In the theme extension, it simply overwrites this. The extension file has a similar folder structure (\graphics\graphics_misc.xml), and references the exact same line above. However, it contains a separate folder of graphics that overwrite the 3.5E.pak graphics.Quote:
<icon name="button_people" file="graphics/sidebar/button_people.png" />
It may not even be possible to do what I'm thinking... essentially, "icon name" for button_towns, etc., is being defined in two extensions simultaneously (or sequentially? I have no idea how extensions are loaded), and naturally, the actual extension file is taking precedence...
EDIT: As I'm writing this, I'm answering my own question. FG2 appears to load extensions alphabetically (I think?) -- so renaming my theme extension to z.blah blah blah loads it after the Town/Shop extensions, and everything works swimmingly now :)
PS - Attached my theme extension if you're curious as to what it looks like. :) (link is below from my dropbox, appears to be too large for the forums).
https://www.dropbox.com/s/oqjxs5gjebn9143/Wood.zip
Oh sweet, glad you answered your own question and got it to work. :)
Very cool extension by the way, I like the wood feel.
I wish I could take credit for it, it's an old theme that I think Dr. Z did, and/or was from FG2 offficially, with some revised sidebar graphics to give it a "Pathfinder" feel. I should actually check with those guys and see if they mind me "re-releasing" it as such :)
You should probably just add the <loadorder> tag to properties and set it to something like 15 in your skin.
Perfect, that did it - thanks for the tip, didn't know that was an option. Sorry for having derailed the thread, <3 the shop/town extension :)Quote:
Originally Posted by Griogre
Brad - quick note, thought you might enjoy some tools I put together to automatically populate town inventories in FG2, using TableSmith.
Planning to automate Towns & NPCs next for XML-friendly output with your extensions.
https://www.fantasygrounds.com/forum...915#post128915
Hey everyone!
Quick question about this EXT. Besides being a cool way to create Towns and Shops ahead of time (basically GM organizational stuff), are there any other aspects to this EXT that aren't obvious? Such as, do players ever see this info? Is there a way to drag a shop or town onto a region map or something?
Thanks
Emrak,
You kind of have to keep track of towns on maps by yourself at the current moment. My lack of scripting knowledge and my current players not giving a crap about the data has kind of put this ext on hold for me, but it's not dead. As soon as I can get some free time I have some good ideas at a revamp including adding options for the kingmaker rules in there as well. If you have any requests or want to help it might get me off of my butt :)
-Brad
Ya, this is extension is cool as hell. I was really diggin' it. Hope you can find some time for it.
Paging Brad - I have sent you a PM about the extension. Just in case you didn't see it, can you message me.
Thanks
Toph
I tried to add this extension on a just started project but I could not. And when I try to use the extension in a new one I get the message below:
Ruleset Error: window: Control(filter) anchoring to an undefined control (rightanchor) in windowclass (townlist)
Ruleset Error: window: Control(filter) anchoring to an undefined control (rightanchor) in windowclass (townlist)
Script Error: [string "campaign/scripts/campaign_list.lua"]:11: attempt to index field '?' (a nil value)
Ruleset Error: window: Control(filter) anchoring to an undefined control (rightanchor) in windowclass (townlist)
Ruleset Error: window: Control(filter) anchoring to an undefined control (rightanchor) in windowclass (townlist)
Ruleset Error: window: Control(filter) anchoring to an undefined control (rightanchor) in windowclass (townlist)
Ruleset Error: window: Control(filter) anchoring to an undefined control (rightanchor) in windowclass (townlist)
I'm using the 1.6 version with the last updated FG (Pathfinder V3.0.1).
Could you please help me?
I would imagine this extension (and others developed for FG 2) will need to be updated by the developer (or someone else) to work with FG 3.0.
I've been waiting to see if anyone was still working on this that would update it.... *watches from afar*
hi Folks
I had a look at the extension code before the holidays to see if I could make it work with FG 3. The main issue is that the extension does not play nicely with the more standardised template structure in FG3. I have been trying to get my head around how windows are handled and understand the logic, but cannot get windows to appear. If someone has some sample code that can make a blank form appear I can probably take it from there.
I have made a bunch of extensions to this extension in 2.9 which I want to bring into 3.0 once I can get the windowing working. These include affiliations (eg. guilds & clans etc), locations (temples, shops, taverns)..stuff that makes a free flowing campaign a bit easier to manage
All the best
Toph
The main thing to look at is the window classes being used (to see if they are valid) and the frame for the window. For example, the shop extension does not work in 3.0 because the "shoplist" class has a <frame> of "scrollboxfortabs" which does not exist in CoreRPG - use a frame of "campaignlistwithtabs".Quote:
Originally Posted by brochr
Additionally, open the console window to see warnings - type /console in the chat window. This will help to identify items that are not recognised or have changed in FG 3.0.
Hi Folks
A BIG thank you to Trenloe for doing a quick update for the Shop Database to make in compatible with FG3.0 and to work with the CORERPG engine. I have polished it up a little to make the look and feel closer to FG 3.0
We have tested it with CORERPG, Pathfinder and 3.5E and the same version works for all. It should also work with other rulesets without modification.
I have also updated the Town database in the same way and it should also be compatible with most rulesets.
Apart from the code updates, the file naming is now further simplified as there is no need for different branches for the D&D and Pathfinder rulesets.
With Brad's agreement I will be doing some further work based on these extensions and I am interested in comments on the following developments I have done.
Places Database:
This extends the "shop" idea to cover all kinds of locations - temples, taverns, hideouts, castles etc. My current code has five tabs:
- Main: fields: place type, alignment, deity, clientele, GM notes
- Notes: free form descriptive text
- NPCs: links to NPC & Groups associated with the place
- Story: links to Story entries associated with the place
- Inventory: inventory items available at the place, the prices and links to library item records
Groups Database:
This adds a way to keep track of groups or affiliations in game, like clans, tribes, religious organisations, secret societies etc. It allows you to add NPCs and keep track of their relationship (e.g. member, enemy, friend etc)
My current code has five tabs:
- Main: fields: type, alignment, scale, GM notes
- Notes: free form descriptive text
- NPCs: links to NPC associated with the group and their role
- Story: links to Story entries associated with the group
Please feel free to comment or suggest additional fields. I will release a beta in about a week or so.
I will also update the Town database to link to these databases once any bugs from the conversion have been dealt with.
All the best
Toph
I would suggest structuring this like the group design in the Magic Schools section of Inner Sea Magic. (The structure is for any kind of organization.) This would include Entrance Fee, Entrance Exam skill check, Tuition/Dues, Associated Skills, Semester/Membership Term, and Expulsion fields as well as a bullet list for boons and awards. The skills could even possibly have buttons that would roll the skill for the selected character.Quote:
Originally Posted by brochr
These look pretty nifty. I am testing them out in my Custom CoreRPG ruleset and they seem to work just fine.. but maybe the graphics are tweaked a little bit... not sure if it's a problem with the extension or with compatibility with my ruleset... I'll do more testing to see.
The scrolling on the first page of the 'Town' extension goes out of the top of the box, the scroll bar gets lost under the tabs at the right, and the spacing on the 'Shops' tab seems to be double spaced.
Also there is no 'close' box on the Town sheet.
Clicking out of a box does not remove the focus.
It would also be nice to pick up the 'lock' code from 3.0 and hide empty fields when locked.
The golden rule for any extension written for CoreRPG, but running in another ruleset layered on top of CoreRPG, where issues are seen is to test it in a purely CoreRPG campaign to see if the issues occur in CoreRPG itself.Quote:
Originally Posted by Blackfoot
My thoughts exactly, and yes, the graphical issues are part of the Town Extension.Quote:
Originally Posted by Trenloe
The scrollbar is covered by the tabs at the right of the Main Tab.
The Main Tab scrolling position is off and scrolls out of the top of the box.
The 'Shops' and 'NPCs' Tabs are double spacing. Less spacing would be good visually and allow for more Shops and NPCs per town without scrolling.
And there is no 'Close Box' for the Towns.
The focus clearing issue seems to be a problem in 3.0.2.. not related to the extension.
Also.. the extension's fonts are overwriting ruleset/extension fonts. I realize that you need to include the extra font types because they are not part of CoreRPG... I'm not sure if there is a good solution for this.
Extensions are always going to have the possibility of overwriting other extensions. Which extensions are you seeing a clash of font names in?Quote:
Originally Posted by Blackfoot
A quick look at the current 3.5e, PFRPG, 4E, Call of Cthulhu and C&C ruleset (all the major commercial rulesets layered on CoreRPG) shows that they don't contain the font names used in the town extension - so there is no clash for these rulesets.
Which rulesets are you seeing a clash of fonts in?
When it comes down to it, the font names used in the town and shop extensions are the direct mapping of the similar fonts in FG 2.9 rulesets, and they use the CoreRPG supplied fonts so they are not actually "overwriting" fonts.
There will always be the chance that such a generic extension as these (and other extensions written for CoreRPG) that there will be a clash somewhere.
Any theme that does major Font control is going to have an issue with it. I'm not sure that there is a work around.. other than it defining it's own font unique labels for the fonts it wants to replace/add.
So, no specific themes or rulesets? Your comment was just Generic?
I actually disagree with this comment.Quote:
Originally Posted by Blackfoot
Assuming a theme that "does major Font control" is replacing the base .fgf font files to change the actual look of the fonts.
If such a theme uses the same font file names as CoreRPG then extensions like the town and shop extension will use the new theme font files (as long as they are located in the usual place: graphics\fonts) - which is what you would want to keep a universal look/feel with different themes.
I'm seeing the conflict in my Champions ruleset because I've done a complete font overwrite as part of the theme... hence I can see the generic issues this can cause.
There is no great solution for it, I guess you could put in some sort of check to see if the fonts exist before overwriting them somehow... but simple would be just to call those fonts something else. When I open the window though, half the fonts are going to look like 'Comic Book' fonts and others will look generic... I don't have a great and easy solution.
These are the font entries in the town extension, they are there to use the 9 point fonts that are supplied with the CoreRPG ruleset:Quote:
Originally Posted by Blackfoot
As you can see, the font file names are pretty standard.Code:<font name="sheetnumbersmall">
<fgffile name="graphics/fonts/bold-9.fgf" />
<color value="#000000" />
</font>
<font name="sheetlabelsmall">
<fgffile name="graphics/fonts/regular-9.fgf" />
<color value="#000000" />
</font>
<font name="chatitalicfont">
<fgffile name="graphics/fonts/italic-9.fgf" />
<color value="#261A12" />
</font>
<font name="chatbolditalicfont">
<fgffile name="graphics/fonts/bold-9.fgf" />
<color value="#261A12" />
</font>
You'll have an issue with your ruleset whenever any font name uses one of these 9 point fonts. Unless you include fonts that match your theme in your ruleset using these exact font file names.
Looking at Ikael's extensions he usually puts "updated_" in front of most of the things that he does. Perhaps developers for anything that changes should include some label that is unique to their ruleset/extension in front of anything that is not going to be CoreRPG compatible? e.g. you could modify your ruleset so that all of your font changes have "champs_" in front of the names, the town extension could have "towndb_" in front of the non CoreRPG names, the shop extension could have "shopdb_" in front of the non CoreRPG names. So the above font definition for the town extension, for example, might be changed to:
Then the references in the windowclass XML definitions can be changed to use these extension specific labels.Code:<font name="towndb_sheetnumbersmall">
<fgffile name="graphics/fonts/bold-9.fgf" />
<color value="#000000" />
</font>
<font name="towndb_sheetlabelsmall">
<fgffile name="graphics/fonts/regular-9.fgf" />
<color value="#000000" />
</font>
<font name="towndb_chatitalicfont">
<fgffile name="graphics/fonts/italic-9.fgf" />
<color value="#261A12" />
</font>
<font name="towndb_chatbolditalicfont">
<fgffile name="graphics/fonts/bold-9.fgf" />
<color value="#261A12" />
</font>
In this case, used in conjunctions with the Champions ruleset they will always use whichever font is available in the graphics/fonts directory that matches - so they can be overwritten by a ruleset or theme extension.
I'm actually a little surprised that the small font definitions aren't included in CoreRPG since the fonts themselves actually are.
On a side note: This item is defined incorrectly in the Town file... it should be bolditalic-9.fgf
Code:<font name="chatbolditalicfont">
<fgffile name="graphics/fonts/bold-9.fgf" />
<color value="#261A12" />
</font>
Me too.Quote:
Originally Posted by Blackfoot