Symbaroum Show-stopper Bug

[AKB]

I'm getting various crashes doing unusual things with this product, but can work around most of them. The one that is stopping me proceeding is that tables cannot be opened once created and closed. Creating a table does not show a red dragon icon to start with on the table list. Once the table is built, closing it means it can never be opened again: clicking on table opens nothing and red dragon icon cannot be dragged as it doesn't exist.

I noticed that if I drag the red dragon icon from the info card for table to the hotkeys bar, I can then access the table later, so this seems like a pretty easy bug to fix. It doesn't work as a general work around though, as I have need of very many tables, and linking them is also not possible.

[Mirloc]

Duplicate post, please ignore. :)

[Mirloc]

I just finished testing this, and I don't see what you are describing. I created a new table populated it, closed it and was able to close the tables and re-open it to see the tables listed.

What extensions and modules are you loading?
Some books contain tables (the 5th Ed Player's Handbook for example loads a boat-load), and your table could be lost OR the GROUP tab is selected for (for example) Player's Handbook and your custom table is not showing simply because you are filtering to only see the PHB tables.

29512

EDIT: Sorry for the low-res image, I just wanted you to be able to see the dropdown I was referring to.

[AKB]

29513
29514

I have purchased several rulesets, including 5e, Savage Worlds, CoC. I have no mods installed at all with Symbaroum, it is just vanilla and I just purchased it. All modules native to Symbaroum have been selected in library. The first screenshot shows my building the test table, which looks ok. The second one is after I have closed the table, showing no red icon on this list, with another test table called Treasure that has the same problem. Clicking on these tables does nothing. I have created 100s of tables in 5e and especially Savage Worlds with no problem. I had problems with updates but can update fine now (can enclose update file if that helps).

I am 99% sure this is a problem specific to Symbaroum, as the ruleset show signs of being 90% done, but has some very rough edges. It is also possible it is some kind of data corruption from downloads, but given that nearly everything else works in my system and I'm running a huge 5e campaign at the moment successfully, that is hard to believe... unless only my Symbaroun files got corrupted somehow after having just loaded them.

[Zacchaeus]

It looks like something might not be right with your install. Try deleting the ruleset and the CoreRPG ruleset from your rulesets folder in FGData and do an update.

[AKB]

Thank you, sir. Will try that now.

[AKB]

No ruleset called Symbaroum in the rulesets folder. I deleted and updated corerpg and that didn't do it.

Contents of rulesets folder:
29516

[Zacchaeus]

Oh, it may be in your vault directory then. Try deleting it from there.

[AKB]

Nothing called Symbaroum in vault either, but could be the SFRPG that is only one updated other than Coreprg since I purchased it. I deleted both of these in both rulesets and vault then updated, then created a new Symbaroum campaign with no mods or extensions and tables still have the problem.

Vault folder:
29517

[AKB]

Reply above. Apologies for not using reply to start.

[Trenloe]

The ruleset file in the vault directory is IPFGSRPDRULESET.dat it uses the FG product code, which can be found at the bottom of the product store page, below the screenshots.

[AKB]

Found file and deleted it. As you said, this caused all of the Symbaroum files to be reacquired in update, which didn't take long. Created new vanilla campaign and had same problem. Can you create tables that reopen in Symbaroum?

[Zacchaeus]

Tables are available in any ruleset which is built on the CoreRPG ruleset. I'm assuming that this one is too.

I'm still inclined to something not having installed or updated correctly but I don't know enough about this ruleset to advise further. It clearly should work as noted in post #2 above.

[AKB]

If you try this ruleset out, it is very unstable and easy to crash, so the implication that the CoreRPG stuff should work great assumes a level of stability that isn't there. This is why I am pointing out that while I have found work-arounds for every crash so far, this one stops me from proceeding. So this is a bug report, and unless you cannot reproduce it using the ruleset, I am not sure why you are responding other than trying to understand how to reproduce it.

Is there somewhere else to get customer support from people who have this ruleset installed and at least can determine if my bug report can be reproduced? If this is the case, I am glad to try a very painful full reinstall from scratch, given that I have many campaigns and have been using this product for years and have active campaigns going.

[LordEntrails]

If you try this ruleset out, it is very unstable and easy to crash, so the implication that the CoreRPG stuff should work great assumes a level of stability that isn't there. This is why I am pointing out that while I have found work-arounds for every crash so far, this one stops me from proceeding. So this is a bug report, and unless you cannot reproduce it using the ruleset, I am not sure why you are responding other than trying to understand how to reproduce it.

Is there somewhere else to get customer support from people who have this ruleset installed and at least can determine if my bug report can be reproduced? If this is the case, I am glad to try a very painful full reinstall from scratch, given that I have many campaigns and have been using this product for years and have active campaigns going.
Please give us step by step instruction on how to repeat the crash. With the information given so far, no one has been able to reproduce your issue.

[Trenloe]

Please give us step by step instruction on how to repeat the crash. With the information given so far, no one has been able to reproduce your issue.
1) I don't think the OP is actually having "crashes" as we’d think of a "crash" - i.e. the app stops working completely and exits. I think the OP describes issues they’re having with functionality as "crashes".
2) The specific issue raised in this thread is shown in post #4.
3) To be fair, I don’t think anyone who has the Symbaroum ruleset has actually tried to reproduce this issue.

So, yes, it would be nice if FG users who have this ruleset try to reproduce the issue detailed in post #4.

[Kelrugem]

Hi :)

I have that ruleset, too, but didn't use it yet. I just tested that and you're right, adding tables only works when you press "Add table by size", "Add item" does not work (one does only get an empty item which can not be edited). Also when one uses "Add table by size" and creates a table etc. then one can indeed not open this table anymore after it was closed. I do not know if the creator knows or wants the functionality of tables because all the provided tables by the ruleset are just images of the tables from the book/pdf and not tables you could roll on :)

There is a Symbaroum ruleset thread where you can describe your issue(s): https://www.fantasygrounds.com/forums/showthread.php?48743-Officially-Licensed-Symbaroum-Ruleset!

Have fun :)

EDIT: Ah, now I see that you already reported this there :)

[AKB]

Thank you Trenloe. A quick summary of this table bug and I'll also give a few actual crash bugs to be helpful, even though I can work around them for the time being. Please note that it is only because I love Fantasy Grounds and Symbaroum that I am being so persistent. I'm not intending any trolling here, and can wait for fixes for this very new ruleset:

Table Bug
1) Install fresh version of Symbaroum with no mods of extensions selected. Load modules Symbaroum Core Rulebook, Symbaroum Core Rulebook - Player's Guide, and The Promised Land
2) Click on Tables
3) Click on List editing icon in the lower right of Tables list window.
4) Use Add Table by Size widget and select 2 and = from the radial menus.
5) Name table "A Test" and note the the usual square red draggable dragon icon to the left of the table does not show on table list, but does show on table info card.
6) Fill the 3 fields in on table and close the table.
7) Click on "A Test" on table list. It will not open and no icon shows, making it forever uneditable as far as I can see.
TIP 1: If you drag the red icon from the info card to the hotkey bar you CAN use this to access the table via hotkey, so this bug seem very minor being only the lack of updating the icon and link on table list.
TIP 2: If you use the radial menu instead of the List editing icon to add the table to start, it cannot be edited at all and doesn't look like a table.

Has Effect "crash"
1) Fresh install as above.
2) Add either a Trait or an Ability
3) Add Action button.
4) Click Has Effect regardless of what kind of action is selected.
5) Get this text in chat box "s'hasEffectToggled: Wants effect. New node:' | databasenode = { abilities.id-00001.actions.id-00001.effect }"
NOTE: These features are extremely powerful to add new Traits and Abilities and among the most sophisticated in any FG ruleset, but they seem to be 90% done.
TIP: All changes to Has Effect are lost and on a related issue, when you put a roll in the main action or trait section then click Is Contested, the second value you select will not show when you open the info card again... however, it WILL retain the set value, so it does work for contest.

Actual crashes
If necessary I will go into more detail on this, but if you copy a creature and then edit it and also apply a CUSTOM trait or ability, it is not hard to get script errors popping up that seem to corrupt the live data (no lasting data corruption found yet, but worried) so that other bugs start occurring. The can be worked around by using the process of elimination to find out what the code doesn't like and avoiding it. Again, seems at least 90% done, but the script errors make it scary to proceed with building a large campaign fearing data corruption.

Thanks in advance for any help!

[Trenloe]

@AKB - I think you referring to errors/warnings/issues as "crashes" is confusing people. As I mentioned in my previous post, computer application "crashes" for most people is when the whole application stops running - usually exiting or not-responding at all and you need to restart it. Here's some info on what most people think a "crash" is: https://en.wikipedia.org/wiki/Crash_(computing)

So, FG not doing what's expected, raising errors, or just warnings - but still continuing to run, is not a "crash", but you referring to these as "crashes" is very confusing.

I get it, there are some issues your having. Thanks for providing details of the table issue. @Kelrugem has verified this as an issue.

If you are getting script errors, please provide actual details of the error message (you can click the "Copy to clipboard" button in the Console that displays the errors), and what you were doing when the error occurred. This information is vital to give the developer a chance to track down the error and fix it. I'm sure they'll appreciate as much information as you can provide.

[Trenloe]

Has Effect "crash"
1) Fresh install as above.
2) Add either a Trait or an Ability
3) Add Action button.
4) Click Has Effect regardless of what kind of action is selected.
5) Get this text in chat box "s'hasEffectToggled: Wants effect. New node:' | databasenode = { abilities.id-00001.actions.id-00001.effect }"
Yeah, not a "crash". And, in fact, that isn't even an error. FG "errors" are displayed in red text in the FG console window that pops up when the error occurs. Text in the chat box like that looks like debug code left in by the developer. Thanks for reporting, I'm sure the dev will check it out soon.

[AKB]

You are correct that the FG app has never crashed to desktop. However, I can make the Symbaroum crash in the sense that it gets a script error that will not stop happening. So I am here referring to the Symbaroum module crashing, not FG. Note that I never referred to the table issue as a crash, only as a bug. I then mentioned that Symbaroum is generally unstable (true), and that I can get it to crash (true when crash means that it is dysfunctional enough to have to be restarted). I also mentioned that I can work around everything except the table bug, so this shows I am not trying to unfairly disparage FG or the ruleset, just reporting on the facts.

[AKB]

I will reproduce the script errors, but, again, it is the table bug that has been confirmed that is my biggest issue at this point. I can avoid the script errors by restricting how I use the system, so this is not critical, but I need the tables to build the sandbox among other things. It would be fantastic if Symbaroum also fully de-bugged the excellent Abilities/Traits/and Custom NPCs that it seeks to support, so I will take the time to recreated and post script errors ASAP. In the meantime, please forward the table bug. My 5e campaign is over halfway done and I need to start working on the next campaign, which will take months of work... I'd love it to be Symbaroum!

[AKB]

OK, first script error occurred in seconds:
1) Click on NPCs
2) Drag icon for NPC "Voiling" down so it is copied and shows on list (done this 100s of times in 5e and Savage Worlds).
3) Open new NPC by clicking on "Voiling"
4) Click on padlock to unlock.
5) Get error "Script Error: [string "campaign/scripts/npc.lua"]:15: attempt to call field 'update' (a nil value)"

Next a deeper level of this kind of custom NPC update.
1) Click on abilities and create new ability named "Diseased Bite" have it only be a roll (which sometimes works) as a contest, but also check the Has Effect checkbox (mentioned prior)
2) Assign this ability to the prior Voiling.
3) Put into combat tracker and then try to use this new ability after targeting PC.
4) Try to click on the ability as you can with other abilities.
5) Generates this error "Script Error: [string "campaign/scripts/npc.lua"]:15: attempt to call field 'update' (a nil value)
Ruleset Warning: windowlist: Could not find empty font (list-empty-ct) for control (list) in windowclass (combattracker_host)
Script Error: [string "scripts/ability_effect_button.lua"]:15: attempt to index a nil value"
6) While this time I could not reproduce it, I dragged a standard NPC into combat tracker and was able to create script errors after doing the above, even after removing the custom NPC from tracker. Restarting Symbaroum was enough to clear that problem in that case.

So far, again, my biggest and most consistent script errors are on and around adding Abilities and Traits and creating custom NPCs. Besides this (which is very unstable) and the tables issue, I have encountered no other problems. Then again, I only got 1% into designing my campaign and was stopped cold by the table bug.

[AKB]

I understand that the main developer on this has recently moved, but I'm going to bump this issue so that they can, hopefully, be informed about it when getting back to work on this.

[Simpe]

Hi AKB!

Sorry for the late answer.

Unfortunately yes I have moved last thursday and hopefully I should have internet access again before the end of this week! As soon as that happens I'll finish up the most recent work and patch the module. The main issue which you have has been solved.

The second one I haven't looked into much unfortunately but judging from the error it should be a fairly easy fix, thank you!

Please keep a lookout in the official Symbaroum thread for when I send patches to SW!

Thanks,
Simon