I'm having some trouble with changind roll formula for T20

[solivem]

Hey, how going?

I'm having somre trouble with roll for Tormenta20, i've alreadry changed the formula for "1d20 + @actor.system.pericias.ladi.value" and so many diferents versiosns of it. And still nor rolling, like in Perceptive wiith the same formula it's going nice, but with Lock & Key is not working. Any ideia how can i make it work?

[Saibot393]

The formula seems to roll for me, so it probably isn't the problem. Could do the following:

• Enable the Lock & Key setting "Message popups" and the Core Foundry setting "Scrolling Status Text"
• Try to use the above formula again (probably for Lock picking?) and see if there is any text above the lock that might explain why it isn't working
• Open the console (F12) and see if there is any output there when using the lock action

[solivem]

Ok, i've tried an show this message:

SyntaxError: Expected "(", "{", "ᚖ", [+-], [0-9], [^ (){}[]$,+-*%/], [a-z$_], [dD], or whitespace but "," found.

[Saibot393]

That is probably a console error message, right? Could you send me a screenshot of the message, including the line info at the end?

[solivem]

Ok, is that the message in console.

[Saibot393]

So, it seems like lock break formula includes some invalid characters/characters that can not be parsed correctly by foundry roll formulas, what is the exact content of your Lock & Key setting "Break lock roll formula"?

[solivem]

Right, all the formulas:
lockpicking: 1d20 + @actor.system.pericias.ladi.value
Break: 1d20 + @actor.system.atributos.for.value
Magic: 1d20+@actor.system.pericias.mist.value

There's actually any other module that might be conflict?

[Saibot393]

While it is theoretically possible that it is a module conflict, the module in question would have to somehow influence the foundry roll formula logic, which i have not seen so far.
I have a few ideas what could cause the problem but i would have to it up close, could you send me the world file of the world you used to test Lock & Key (i would need the world.json file and the data directory found in Foundry Data>worlds>"your world name").
Alternatively, have you changed any Lock & Key settings for either the lock, the token, or any of the items of the token you are testing with?

[solivem]

I've changed somethings, but i always turn back do default settings while testing. I've uploaded the world folder to my drive, here's the link:
https://drive.google.com/drive/folders/11m_YzrZF5uetVm8iVlqpYflIPvQrxh2w?usp=sharing

[Saibot393]

I found the bug, for some reason some of your actors have the token lock & key settings configured in a way, that replaces all formulas with ,, here an example:

To reset these settings for all tokens in a given scene, you can use this macro:

let vUpdate = {
  flags : {
    LocknKey : {
      CCFormulaFlag : "",
      CCFormulaOverrideFlag : false,
      LBFormulaFlag : "",
      LBFormulaOverrideFlag : false,
      LPFormulaFlag : "",
      LPFormulaOverrideFlag : false,
      LootFormulaFlag : "",
      PickPocketFormulaFlag : "",
      PickPocketFormulaOverrideFlag : false
    }
  }
}

let vTokens = canvas.tokens.placeables.map(vToken => vToken.document)

for (let vToken of vTokens) {
  await vToken.update(vUpdate);
}

To reset these settings for all tokens on all maps, you can use this macro:

let vUpdate = {
  flags : {
    LocknKey : {
      CCFormulaFlag : "",
      CCFormulaOverrideFlag : false,
      LBFormulaFlag : "",
      LBFormulaOverrideFlag : false,
      LPFormulaFlag : "",
      LPFormulaOverrideFlag : false,
      LootFormulaFlag : "",
      PickPocketFormulaFlag : "",
      PickPocketFormulaOverrideFlag : false
    }
  }
}

let vTokens = [];

for (let vScene of game.scenes) {
  vTokens.push(...Array.from(vScene.tokens))
}

for (let vToken of vTokens) {
  await vToken.update(vUpdate);
}

To reset these settings for all actor prototype tokens, you can use this macro:

let vUpdate = {
  flags : {
    LocknKey : {
      CCFormulaFlag : "",
      CCFormulaOverrideFlag : false,
      LBFormulaFlag : "",
      LBFormulaOverrideFlag : false,
      LPFormulaFlag : "",
      LPFormulaOverrideFlag : false,
      LootFormulaFlag : "",
      PickPocketFormulaFlag : "",
      PickPocketFormulaOverrideFlag : false
    }
  }
}

let vTokens = Array.from(game.actors).map(vActor => vActor.prototypeToken);

for (let vToken of vTokens) {
  await vToken.update(vUpdate);
}

You may have been right as this could be caused by a module compatibility problem. The fastest way to check would be as follows:

1. Use a (new) token where you make sure that the Lock & Key settings are empty/unchecked
2. Start running Find the Culprit!
3. Open the token settings, change something outside the Lock & Key tab (e.g. name) and hit save, reopen to see if the lock & key settings have changed If that is not the case, the current module configuration is probably safe