Vaesen Bug Report Thread

I am experiencing an issue with the Apply button in the combat tracker Attack Resolution section. The log says "bad argument #3 to 'format' (number expected, got nil)". Logs attached.

When reporting, please provide more information on the steps are you are taking for us to replicate the issue. I placed a check there to make it a value in case it does come up nil. The fix was pushed a hotfix.

Thanks for your attention. In the combat tracker, I roll an attack against a player character (I don't think the target kind is important). I then open the Attack Resolution of the target and attempt to apply the damage using the Apply button. Since the hot fix, it now reports a new error when calling addShortcut in managerActions.lua line 251 (logs attached).

Thank you. I was able to zero in on the issue for that button. Pushed another hotfix for the combat tracker issue

Thank you. Can confirm that it is now working for me with the latest patch.

I was exploring the headquarters feature and found that I can't add any upgrades (Facilities, Personnel etc.) to a headquarters record. I don't know if this is a bug or just something unfinished. The XML in the rule set looks plausible to my untrained eye.

In summary I opened the headquarters form, added a headquarters and then tried to use the + buttons and dragging upgrades into the four regions with no result (nothing in the log). Maybe I'm doing something wrong. It is simple enough to use a story record to store this info.

Attachment 64147

Pushed another hotfix for this issue.

Great -- dragging now works for me in the headquarters. The green + buttons are a bit weird -- like the hotspot is not aligned with the button properly - you seem to have to click them near the bottom, but now I know that's fine. Certainly not showstopper.

Thanks again. Hopefully I'm done now :)

Unfortunately, I found another issue. When using the character creation wizard, Characters->PC Builder->Equipment (see attached image), the Pre-Defined equipment slots are not displayed.

Attachment 64192

The changes we've made recently didn't touch that area of the ruleset. I will take a look and see what is the issue, but it may take some time to tackle it.