PDA

View Full Version : My players are having issues having access to modules in our game.



Quixdraw21
December 20th, 2021, 17:10
Hi,

My players are having issues not having access to the available content from the modules I have in use for Deadlands Horror at Headstone Hill.

I know the modules are activated and made open to them, but it is still not working.

Advise?

Thanks,

Marshal Patrick

Zacchaeus
December 20th, 2021, 17:20
Can you define not having access? Do they not see the modules in their activation screen? Or do they see them and can't load them?

Quixdraw21
December 20th, 2021, 17:54
They can't see the module content.

Moon Wizard
December 20th, 2021, 17:57
Some questions:
* Is the module marked with a green check mark in the GM module activation window to allow players to access?
* Have the players activated the module on their end in the Player module activation window?
* Which specific modules are players not seeing in their Player module activation window?

Regards,
JPG

Trenloe
December 20th, 2021, 18:00
Looking at the final screenshot on the product page here: https://www.fantasygrounds.com/store/product.php?id=S2P10225

It looks like there are two modules: DLWW: Horror at Headstone Hill and DLWW: Horror at Headstone Hill Player Introduction - the players should only activate the DLWW: Horror at Headstone Hill Player Introduction module. The main module (the adventure) shouldn't be opened by the players, with data being shared individually to the players as needed (via the right-click - share functionality).

Zacchaeus
December 20th, 2021, 18:00
Ok so just to be clear your players can go into the activations screen and they see the modules in there. They click the Load button and the module shows that it is loaded. But when they them click on say items or classes or backgrounds from the right hand buttons they see no items from that module? Or if they look in the library they don't see the module in the library or when they click on it they don't see the contents?

Can you maybe provide some screenshots so we know what the problem is exactly.

Quixdraw21
December 20th, 2021, 18:10
50507
50508

No items come up.

Trenloe
December 20th, 2021, 18:30
As the GM click on the red X in the module activation window for the Player Introduction module to change it to a green tick to allow the players to activate the module. This will give the players access to the module, which they have to activate - it contains a library reference manual with some entries related to the players and some images - no other data is provided in this player module.

Note: there are no archetypes with this adventure.

Quixdraw21
December 20th, 2021, 19:50
The modules are already checked green and this involves two new players. My previous players are having no problems. This was after the latest patch, btw. I'm betting that is the cause.

Trenloe
December 20th, 2021, 20:00
The modules are already checked green and this involves two new players. My previous players are having no problems. This was after the latest patch, btw. I'm betting that is the cause.
Have the players updated to the recent version?
Have you 100% confirmed that the players have activated the player module? The screenshots provided earlier don't show the module activation screen, so we can't tell.

Quixdraw21
December 20th, 2021, 20:06
I will double check that it is activated on their end. I believe they have the latest versions. Though, how would both more recently joined players be having this same issue when my other 3 older players aren't?

Zacchaeus
December 20th, 2021, 20:08
Well first we need to eliminate user error. Some screenshots from the players activation screens would be useful.

Quixdraw21
December 20th, 2021, 20:09
Ok, let me get back to you.

johnecc
December 20th, 2021, 21:58
Hi, Zacchaeus can correct me if I am wrong, the Archtypes come from the main rulebooks, do the players have that loaded, and also, I don't believe that players will see anything in Assets, that is purely for GM's.

Quixdraw21
December 21st, 2021, 22:21
I got it sorted. It was a temporary problem. Thanks