Printable View
After this hotfix, now when I change the MOD for strike rank, Strike Rank instantly sets to 0 and never changes. So, for example, if I start with a Strike Rank of 5 and I mouse wheel or enter "1" in the Mod box, Strike Rank instantly becomes 0 and never changes.Quote:
Originally Posted by superteddy57
This was working fine until the hotfix went through.
Is this replicable for anyone else?
Regards,
Devin
I pushed one more hotfix. Looks like I forgot to include a check in the code and it always assumed the option was turned off on the character sheet.
OK. Thanks.Quote:
Originally Posted by superteddy57
Used the new general hit point mouse wheel indicator in last night's game. Love it! Very easy to use. Thank you for that great enhancement.
Did not get to try the SR modifier last night but looking forward to using it next Saturday.
Regards,
Devin
Regarding setting wounds by using the mouse wheel. It works when hit locations are on but when they are not, it doesn't work.
In the line "local bHRUHL = OptionsManager.isOption("HRUHL", "on");", in the function below, bHRUL is bFALSE if hitlocations are off.
Should you even need to test if hit locations are on or off? Wouldn't you want the mouse wheel to always work?
Code:In wounds on charater main:
function onWheel(notches)
local bHRUHL = OptionsManager.isOption("HRUHL", "on");
if not Input.isControlPressed() or not bHRUHL then
return false;
end
self.setModifier(self.getModifier() + notches);
return true;
end
It could still be enabled, but this was my solution for the time being for when hit locations are enabled. I had no time to test further for other scenarios. This ensures a modifier is used when hit locations are enabled and don't interfere with normal wound calculation for that state. I would think since the wound box is editable, it would be faster to just type the wounds and it factor the wounds normally as its not pulling from other sources to calculate your final wounds.
OK. Fair enough.
New SR modifier is working nicely. Thank you.Quote:
Originally Posted by devinlc
Great to hear, glad it's working out.
In case it is easy to do, my players have told me that they would love a little fill-in circle next to POW on the Main page of the character sheet so that they can mark when they get a POW gain experience check. Right now, they have to write it down in the NOTES tab. This would be the same fill-in circle you find on the Skills page or in the Melee and Missile section of the Main page.
Regards,
Devin
I'll consider it. Just may be some time since I'm a bit swamped and the ruleset is currently in the beta awaiting release to LIVE.
Hello.
If I enter an NPC and it has a body type of four-legged, if I enter missile hit locations and close the window, when I reopen the NPC, the missile hit locations are blank. Is there any way to make it so that they stay?
I haven't tried all of the body types, but four-legged definitely erases them.
There is a work around, so I guess this isn't urgent. One can just enter the four-legged body type, let the system generate the hit locations and melee rolls, and then change the type to "Custom" and enter in the missile rolls and they are not erased.
Regards,
Devin
I'll add it to my list to look at. Currently buried under other projects, so may take some time to get to it.
After the new update the battle tracker is getting a lot of windowsclass errors and warnings.
And all tooltips are white text on a white background.
Ignore this post.
Did it stop doing that for you?Quote:
Originally Posted by Stollesson
I am getting CT errors. See attached.
Devin
That appears to be an issue with the theme you have selected. The vanilla BRP theme doesn't throw those errors. I would say to post in the forum for the theme to have the dev fix it or post in the support forums if it's a SmiteWorks theme.
OK, I will try another theme. The one I use is a Smiteworks theme, so I will post it on the support forums.Quote:
Originally Posted by superteddy57
Thanks,
Devin
Even the Core Theme gets that error. Any theme I use results in it. Tried with all extensions off, still get the error result.Quote:
Originally Posted by devinlc
Devin
Can you try with all of your extensions disabled? I'm not seeing this with a vanilla BRP campaign.
I did and still get the error. Let me create a new campaign and see what happens.Quote:
Originally Posted by superteddy57
Devin
Started a new Vanilla BRP campaign with no extensions. Got the error message.Quote:
Originally Posted by devinlc
I note that the previous poster was also getting the same messages but then said "never mind". I wonder what happened to them?
BTW, I also get the white on white issue the other person mentioned.
Devin
Did a bit more poking. I notice that the header of the CT seems a bit messed up. That might be the cause of the error. If you look at the attached picture and look carefully at the very upper leftmost part of the CT, you can see what is basically black letters all jumbled together. These seem to be the rest of the headers for the CT that should be alongside Name and Init. If I mouse over that jumble, in fact, I get a tooltip explaining Strike Ranks.
Also, you can see the white on white on the names of the PCs in the upper left of the screen.
Devin
I believe it's the theme with the combination of the extensions you are using. Here is the desktop with no errors and how the CT should look when opened.
Attachment 61553
Weird. As I said, I created a new campaign with no extensions and no theme and still had the issue, but I will poke into it more and see what I can see.Quote:
Originally Posted by superteddy57
Devin
I can suggest deleting the ruleset in your rulesets folder and then doing another update to download a fresh copy. This can be accessed from the folder icon on the first screen you see when starting FG. I would suggest only the ruleset and no other files.
Thanks. Fixed.Quote:
Originally Posted by superteddy57
I need to remember that!
Devin
Just pushed an update that should address the Wood theme nameplate coloring issue. Please run a new Check for Updates.
Regards,
JPG
Yep. That fixed it Thanks!Quote:
Originally Posted by Moon Wizard
When you drop a skill that has a base chance that is a formula (such as dodge) on the character sheet, its base chance is not calculated.
To replicate:
Change the dodge skill in the table "Skills" in scripts/manager_gameline.lua so that dodge reads:
Now dodge is no longer a default skill.Code:["Dodge"] = { Base="DEX*2", Category="Physical", Untrained=true },
Reload the ruleset. Create a new character. Drag the dodge skill onto the character sheet. The base skill value is empty. If you reload the ruleset, you will force a re-calculation and the skill value will be properly calculated.
This is a problem to me because I'm adapting an extension so that all skill base chances are formulas, so when I drag skills to the character sheet the base chance remains at zero.
Thanks for the report. I'll have a look at it when I get a chance.
When a player sets as AFK, the other players can see it, but the GM gets an error message:
[ERROR] Unknown special message type received. (setafk)
I tested this out with my players and with me acting as a player.
Regards,
Devin
Thanks for the report. It's best to place these in the bug report thread as I monitor there.
I think its a CoreRPG issue.
OK. Will post it there if it already hasn't been.Quote:
Originally Posted by superteddy57
Devin
Thanks for reporting. This will be fixed in the Tuesday rulesets update.
Regards,
JPG
I managed to solve this problem as far as my extension goes. However, the problem remains for the ruleset as such.Quote:
Originally Posted by peterb
Pushed a fix for this issue.
Hello.
Having an error with tonight's update only on the player's side when I open the combat tracker with any PC in it. I tried to troubleshoot as much as I could.
Attached is the error message I get.
I did the following steps:
1) Deleted my ruleset and re-did the update. Made sure I did not have an un-packed ruleset folder in there. Still got the error.
2) Disabled all extensions and themes. Still got the error.
3) Logged in with my D&D 5e ruleset and did NOT get the error, so maybe it is something with the BRP ruleset.
Is anyone able to duplicate this?
Thanks,
Devin
Sorry, I'm not able to reproduce this error. Can't find that labelrightanchor control in the BRP ruleset.
Any advice? Should I do a full reinstall of FGU?Quote:
Originally Posted by peterb
I wonder why it is looking for that control in my version but not yours.
Devin