PDA

View Full Version : Noticed New Behaviour With Created Things



UrsaTeddy
February 20th, 2022, 14:32
Greetings,

not sure when this was updated, however I was creating some new Edges/Hindrances for my game and it was noticed that players could not see those creations at all.

I had to share them with the players using the radial menu.

However this behaviour seems non-intuitive since Edges/Hindrances are generally created for players to use/access.

Perhaps someone is creating the data from a Setting Book that they do not own for example.

Are we expected to create modules of new data for players for them to just be able to access the data without sharing it?

Thanks in Advance,
D

Jiminimonka
February 20th, 2022, 17:40
Greetings,

not sure when this was updated, however I was creating some new Edges/Hindrances for my game and it was noticed that players could not see those creations at all.

I had to share them with the players using the radial menu.

However this behaviour seems non-intuitive since Edges/Hindrances are generally created for players to use/access.

Perhaps someone is creating the data from a Setting Book that they do not own for example.

Are we expected to create modules of new data for players for them to just be able to access the data without sharing it?

Thanks in Advance,
D

If you create anything as a DM, it has to be shared with the players before they can use it. It has always been this way.

Everything the players see or have access to is shared by the host.

If you want to share a bunch of stuff, make it into a module and tell the players to load it.

UrsaTeddy
February 20th, 2022, 20:35
However this was not the original behaviour.

The reason I noticed this at first was because I loaded a campaign that was on hiatus over the Christmas/New Year Holidays and players commenting they could not see the things that I had created.

Before the break this was not the case.

I have never used any modules except for the SWADE base rules for GM and Player and two character sheet extensions (Usage Die, Advancements Tab).

All other material is "hand made" by myself. This is the first time I have had to share the data with players.

Thanks for the reply,
D

Jiminimonka
February 20th, 2022, 22:23
However this was not the original behaviour.

The reason I noticed this at first was because I loaded a campaign that was on hiatus over the Christmas/New Year Holidays and players commenting they could not see the things that I had created.

Before the break this was not the case.

I have never used any modules except for the SWADE base rules for GM and Player and two character sheet extensions (Usage Die, Advancements Tab).

All other material is "hand made" by myself. This is the first time I have had to share the data with players.

Thanks for the reply,
D

You must be from the future where FG works differently and have travelled back into the present when it just does what it's always done. Please next time you see The Doctor, get her to grab your computer so we can get that version too ;)

UrsaTeddy
February 20th, 2022, 23:52
All joking aside though .. this is fact.

I run a vanilla SWADE campaign but with a few Hindrances and Edges taken from other sources that I have manually put into the system.

As I said pre-break they did not need to be shared ... so yeah ... future me merged with past me as well as future players merging with past players ... not a big deal at this point - we are dealing with each one as it pops up.

D

Doswelk
February 21st, 2022, 07:42
It is annoying when you forget to share it and yes, I am sure it did not used to be this way too.

But to be honest it is useful, you can create things you will want to share ahead of time now, then share them when the players discover it :)

UrsaTeddy
February 21st, 2022, 07:45
Oh I am sure there are benefits either way ... now I will have to learn to create a module "the correct way" to collect my campaign information together.

Jiminimonka
February 21st, 2022, 09:07
The only way I can think FG was sharing stuff with players without you actually sharing it is if you added stuff to a category or module they already had shared.
Otherwise it was a bug in Savage Worlds that got fixed, no other ruleset was sharing things with players automatically.
But its not important.

UrsaTeddy
February 21st, 2022, 09:55
I was only using SWADE base rules (Player and GM modules).

I was creating groups in the drop downs for my own organisation (for example My Campaign Hindrances).

I was creating the data in those new groups.

You cannot insert new data into the SWADE modules.

So bug perhaps. However as previously stated it was like this until end of November.

FrodoB
February 21st, 2022, 11:48
Otherwise it was a bug in Savage Worlds that got fixed, no other ruleset was sharing things with players automatically.

Or it was a conscious change Ikael did for the ruleset that broke with the CoreRPG update in January (?).

EDIT: I fired up Fantasy Grounds Classic where the last changes were somewhere in last June and it worked back then exactly as it does now - you have to change manually. So maybe there was indeed some bug...

Jiminimonka
February 21st, 2022, 11:50
Or it was a conscious change Ikael did for the ruleset that broke with the CoreRPG update in January (?).

Maybe. Savage Worlds was not built on CoreRPG but Ikael has been moving it over gradually.

Doswelk
February 23rd, 2022, 12:25
Savage Worlds is built on top of Core, but does change a lot, so a change to Core can and does sometimes bork SW.

Of course SWADE breaking also means SWD and SWPF break as they are the third layer of the cake:

SWPF / SWD
SWADE
Core

Lonewolf
March 7th, 2022, 00:35
Or it was a conscious change Ikael did for the ruleset that broke with the CoreRPG update in January (?).

EDIT: I fired up Fantasy Grounds Classic where the last changes were somewhere in last June and it worked back then exactly as it does now - you have to change manually. So maybe there was indeed some bug...

SWADE 5.5 is undocumented. Guessing a minor bug fix against 5.4 change (Changes that where required to prepare Pathfinder)
Since then Core has changes quite a bit. New API and some old functions deprecated

SWADE possible borked suspects reported: Ally NPC rolls; Error in chat when using damage spell.
The jury is still out.

FrodoB
March 7th, 2022, 08:08
SWADE 5.5 is undocumented. Guessing a minor bug fix against 5.4 change (Changes that where required to prepare Pathfinder)
Since then Core has changes quite a bit. New API and some old functions deprecated

SWADE possible borked suspects reported: Ally NPC rolls; Error in chat when using damage spell.
The jury is still out.

Sorry, but I do not understand what your point is (or even what you're saying), exactly?
I was saying that the behavior reported by Ursateddy in the first post is not something that got recently "undone", but instead something that wasn't normal behavior even months back.

Lonewolf
March 13th, 2022, 08:01
Sorry, but I do not understand what your point is (or even what you're saying), exactly?
I was saying that the behavior reported by Ursateddy in the first post is not something that got recently "undone", but instead something that wasn't normal behavior even months back.
Sorry about that. It is me being tired. That is because I am posting at stupid o'clock in the morning, again :o

Just agreeing with you and all of the above. SWADE not updated but behavior has still changed in number of other areas due to Core dependency. Looking into any reported behavior changes is awsome.