Log in

View Full Version : Dice settings not sticking



celebrindal
November 19th, 2022, 12:50
During our session last night I had several complaints from multiple users that the settings for their dice were not staying the same for the entire session.
First noticed on session start, we chalked it up to the new updates for the dice. Everyone set their dice.
An hour or so into the session a couple of people were like, hey my dice just went back to standard black.
Towards the middle of the session this occurred again.

In total during the 4hr session everyone had dice reset to black. I the GM did not. This occurred for some players 3 or 4 times.

Notes: running the PF1E ruleset.
Running a pile of mods, see my forge posting to see what i'm running. 3rd post.
https://www.fantasygrounds.com/forums/showthread.php?75849-Customized-Random-Encounter-Generator-PF1E-Core

Zacchaeus
November 19th, 2022, 13:37
Do you get the same problem without any extensions?

celebrindal
November 19th, 2022, 16:10
No way to tell, since I've got several that are player impacting.

LordEntrails
November 19th, 2022, 16:29
When you have errors and are running extensions and no one else is reporting the same errors with no extensions, then the likely culprit is an extension. To get support for an extension, you need to identify the extension causing the problem, and let that extension developer know. When you use lots of extensions, no one else can replicate your use case without extensive time to do so, something volunteers are unlikely to be willing to do, and since SmiteWorks can't and won't support extensions that they have no control over. You really need to be the one to spend the time to figure out exactly which extension, or combination of extensions, is causing your problem.

Ecks
November 19th, 2022, 18:34
2/3 players in the game I'm currently in are having this happen, in a campaign with no extensions. The GM dice aren't changing. I'll have to mess with it later to see if I can recreate.

Griogre
November 19th, 2022, 22:14
I did have a similar experience last night in my game but as I use extensions I hadn't reported it yet. It seemed to trigger more when players where running multiple characters. I'll see if I can get my Sunday players to test for it. For us it was the player pointer colors.

Ecks
November 19th, 2022, 23:00
Recreated in a new 5E campaign. It looks like this happens when a player is controlling 2 or more characters. Whenever they switch between characters it resets the dice color (and user color) of all other connected players. It also happens when new players join and initially select a character.

Here are steps with 2 players connected (P1 from another computer, P2 via localhost):

GM: Create new campaign, create 3 characters, named Green, Red, and Blue. No other settings are needed.
P1: Connect to game and select Green as character. Set dice color to Green using the color picker
P2: Connect to game and select Red as character. Note on P1 instance that the dice in the tray have changed color to black
P1: Open Dice menu and select color again. Note the old color is still shown in the Dice Color picker, but it isn't active until you click the color and click "OK" again.
P2: Set character Red dice color to Red.
P2: Click Characters and select Blue as a second character controlled by player 2. Player 1 dice color will have been reverted again
P1: Re-select dice color
P2: Set character Blue dice color to Blue.
P2: Select character Red as active (via portrait in top left corner). Dice color of "Red" is correct, but the dice color of Player 1 will revert again
P1: Re-select dice color
P2: Select Character Blue as active. Dice color of "Blue" is correct, but the dice color of Player 1 will revert again


The above steps also demonstrate the issue with the User Color setting (you'll see the User Color indicator dot on the portrait revert for P1 whenever P2 switches characters).

seansps
November 19th, 2022, 23:15
I noticed this same bug in my game on Thursday. No extensions in play. My player set their color in session 0 to green/white. When they logged in for session 1 it was reverted to black. It was the same character and all, only controlling one.

Reg
November 20th, 2022, 04:20
Just in a game where this was happening many, many times.

It also has a PC (artificer) that was controlling two additional characters - his creations

Not sure which extension the GM was running...

sirkerry
November 20th, 2022, 04:43
Had this happen in a PF2 game today. The players settings wouldn't stick, but the GM's where. There was lots of extensions loaded and wasn't able to check without them.

celebrindal
November 20th, 2022, 22:43
I can confirm I did have a player running two characters. Am unable to reproduce at this time due to availability and timing.

Griogre
November 20th, 2022, 23:29
This is happening in a 5E game with no extensions. Whenever a character loads in and the characters already in lose their pointer / dice colors. If you click the portait in the top left if sets the colors back to the original. It also does this if one player is controlling more than one character and switches active characters.

Moon Wizard
November 21st, 2022, 16:10
Thanks everyone for submitting your observations. It turns out that the issue only occurred when more than one player connected, and affected anyone else already connected. I'll be working on a fix for tomorrow's weekly update.

Regards,
JPG

anstett
November 26th, 2022, 14:24
Checking in on a similar problem.
(2E ruleset, many extensions, fully updated)

I had a player mention that they could not assign custom dice to only one of the characters they control. When they made a change (to piercing damage for example) the dice choice replicated across both of her characters.

Is this expected? Or a bug to track down more information on?

Thanks

BOB

Moon Wizard
November 26th, 2022, 20:58
Default dice on the desktop can be assigned per character; but custom dice roll overrides are assigned for all characters in a given system (ruleset).

From your description, I'm not sure if you were talking about the default dice or the custom dice roll overrides.

Regards,
JPG

anstett
November 27th, 2022, 14:00
They were using the new dice pack I gifted them. They set up some custom dice colors per damage type. They made the changes to one Character, then when they went to their second character those changes had been applied to that character also.


On the GM side I had not changed any of the defaults to damage types.

Moon Wizard
November 27th, 2022, 18:39
The dice roll customization settings are per user, per ruleset.

Regards,
JPG

Reg
November 27th, 2022, 23:24
I've just experienced it during FGCon.

During Savage Worlds - Crazy Ivan - One participant was controlling two characters as we were low on numbers due to no-shows. Each time the active character switched, my dice colour reset to black

During Both Star Trek Sessions - as each player selected the character from those available, my dice colour would reset, but then remained fine during play as no further character changes occurred.

During Savage Worlds Super Powers - dice colour reset when initial character selection was happening, then fine during play.

Hope this helps isolate the glitch

Moon Wizard
November 28th, 2022, 00:49
I submitted the fix for this to CoreRPG on Nov. 16. I wonder if the GMs have not updated since then, or are running unpacked versions of CoreRPG.

Regards,
JPG

Reg
November 28th, 2022, 07:39
I submitted the fix for this to CoreRPG on Nov. 16. I wonder if the GMs have not updated since then, or are running unpacked versions of CoreRPG.

Regards,
JPG

I guess that it's possible, but given the last 4 instances that I mentioned were at the official FG Conn which featured multiple instructions all through the sign-up process and registration and joining Discord channels and such to make sure that we were all updated, then it seem somewhat unlikely.

One GM, Lonewolf, Mentioned he was part of the team for SWADE bug checking, so it would seem unlikely.

I'm happy to help participate in any tests to help track this down.

Its slightly annoying, but doesn't stop play

Moon Wizard
November 28th, 2022, 16:07
Hmm, I'm looking at this again this morning, by setting up a host with 2 separate player clients.

Here are all the permutations I tried:
* GM session load and custom die setup
* Player connection and custom user die setup
* Player PC selection and custom PC die setup
* Player second PC selection and custom PC die setup
* Player PC release
* Player session logout

In all those combinations, I did not see any reset of the colors.

Are there any combinations that you are seeing issues with?

Regards,
JPG

Reg
December 1st, 2022, 05:24
Hmm, I'm looking at this again this morning, by setting up a host with 2 separate player clients.

Here are all the permutations I tried:
* GM session load and custom die setup
* Player connection and custom user die setup
* Player PC selection and custom PC die setup
* Player second PC selection and custom PC die setup
* Player PC release
* Player session logout

In all those combinations, I did not see any reset of the colors.

Are there any combinations that you are seeing issues with?

Regards,
JPG

I had a game yesterday that behaved fine, so maybe it's fixed?

I have another coming up on Sunday where one player has control of two NPC allies, and that set it off last time we played two weeks ago.

Possibly that is the only scenario that you have mentioned above?

I'll report back if that game has issues.

Thanks for looking into it.

celebrindal
December 2nd, 2022, 22:52
Have my game tonight, will let you know if the players have issues again as most likely one is away so someone will be running two chars.

Moon Wizard
December 3rd, 2022, 03:58
If you run into an issue, any information about the campaign and/or steps taken would be great.

Thanks,
JPG

celebrindal
December 3rd, 2022, 05:29
We were good tonight. Didn't have any issues. We are all fully patched up.

Reg
December 5th, 2022, 02:48
The game with the player who switches from one PC to two other support NPC's has been and gone, with no issues any more.

Looks like this bug is busted.

Thanks!