setting a permutation results in weird error

[nocturne plover]

ive tried block.Resolve as well and it shows a slightly different error but ultimately doesnt give any more imformation than just failed to set property

[hardy knoll]

what's your block definition look like? do you have a property defined called "detector:inputBlockType" with a bunch of string values?

you can only set block states to values you have listed in your block definition, so if you're trying to use it to store arbitrary data, that will not work

[nocturne plover]

Wdym by property? A component? A permutation?

Nvm

[nocturne plover]

Is there a way to store information on blocks without using property

[hardy knoll]

not directly on the block, no

there's probably some other way to do what you're trying to do, depending on what it is

[nocturne plover]

trying to make a block detect if what in front of it is a certain one, of the users choice.

but If I cant store that directly on the block I dont really know how else I would do that

[hardy knoll]

you can probably store that on a world dynamic property with the key being the block location

[nocturne plover]

yes but if the block is moved in a way that isnt detectable (enderman pickup for one) wouldnt that be a problem?