Hi Chorpa,
I have seen this before but hadn’t related it to having multiple modules open. It sure is a weird one.
I just tested and confirm that the same happens for me.
Hi Chorpa,
I have seen this before but hadn’t related it to having multiple modules open. It sure is a weird one.
I just tested and confirm that the same happens for me.
I took a look, found the problem and fixed it.
I am attaching an extension that will fix it and have emailed Trenloe so he can incorporate a real fix into the ruleset.
Give it a go and if you have any problems let me know.
Ian
MODERATOR: Remove the extension as there is a fix here: https://www.fantasygrounds.com/forum...l=1#post386541 and the extension caused other issues due to an incorrect version compatibility flag.
Thanks for reporting the issue.
And thanks to Ian for (hopefully?) a fix...
I've updated the ruleset to include Ian's fix, and also to fix the library category header issue. It's available here:https://www.fantasygrounds.com/forum...l=1#post387198
Can you please let me know if this fixes this specific issue?
Thanks.
Hey Trenloe
I can confirm that Ian's fix inclusion in the ruleset works like a charm:
- GM encounter lib has now 3 sub entries
- Same for player lib
Thanks for the quick update guys
PS: any status update on the MoreCore migration ?
@Trenloe, I started playing around with the ruleset and libs (for personal updates on some of text references) and i have a couple of question to begin with:
- are you were using any kind of XSD or external tree definitions for your editing?
- which software are you using for XML edition? (dev background here:D)
Thanks guys :)
Welcome to the forums bigjip!
It will be a migration to be layered on top of CoreRPG, not MoreCore. It will be the end of this year/beginning of the next at the earliest.
Nope, I don't use any XSD or external tree definitions.
I use Notepad++ with the XML plugin for editing FG XML.
You are great guys. That was some quick response. Did a quick start up with the new .pak file and it seem to work like a charm now. I'll let you know if I find any more problems on this issue. Otherwise I must say the ruleset work very nice and seems like it's gonna be a long campaign since the players love it. We are gonna run our 16th session next Thursday. :D
Great to hear! :)
Thanks for the feedback and testing.
And, in future, don't let things get to the point that they're really annoying you. Let us know. Although, I may just fob you off with "yeah, sorry, I'll look at it sometime later...." Which might be more annoying! ;)
Nope, because this is the FG child DB node naming and people can delete and remove the child records as they need, so there is never a guarantee that node id-00001 is the Astrogation skill, for example.
If you look at the FG LUA code, you'll see plenty of times where FG cycles through a set of records (a LUA table) using the LUA "pairs" function, and then some field within each DB node will be looked at for a match - usually "name" but could be something else.
ok, make complete sense
I thought this was associated with some kind of schema defined in the ruleset files, tbh i did not spend enough time on this (too busy playing around with the wonderful outcome:D)
I guess i should start by "first-things-first" and look at the tutorials...
Any pointers you would recommend inside all these resources (the wiki, the forum and subforums...) to get started ?
(in the context of the SW ruleset only for now)