v9.0.1, v9.0.2 Fields using data no longer activate when placed.
Psithief opened this issue ยท 2 comments
In v9.0.0 type id was broken. In v9.0.1 and v9.0.2 anything defined with block: '#:#' can no longer be placed - the block is placed without any acknowledgement from PreciousStones. In my case it's '98:3'.
If you added an attempted bugfix here could you please remove it?
In #262 I said
Regarding the one using block data, the data field is saved just fine.
but that was from experience with v9.0.0. I neglected to test blockid+data defined fields in v9.0.1 until now.
I downgraded back to v9.0.0 and it can be placed again, so the configuration is still valid.
Looking forward to v9.0.3.
Same problem here, in my case its "35:2".
Notice: If someone placed a block, it still _poof_s after server restart, in that case its "7".
I'll hope you get to fix that soon.
Version 9.0.3 does not fix that problem!
Version 9.0.4 does not fix that problem!
