Issue description:

Constructor does not place block (anymore after update from old RS version)

What happens:

No Block is being placed
If I select drop, the correct item(s) drops
If I try "/ftb team config ftbu.fake_players true" All I get is an error message because I dont use FTB...

What you expected to happen:

That a block will be placed

Steps to reproduce:

1. Create 1.10.2 world with current RS
2. Setup a basic RS system and try to use the constructor to place a block in the world

...

Version (make sure you are on the latest version before reporting):

• Minecraft: 1.10.2
• Forge: 1.10.2 - 12.18.3.2185 (recommended version)
• Refined Storage: 1.2.25 (latest version for 1.10.2, no change if using others down to 1.2.5)

If I use the old 1.2.4 version of RS again, IT AGAIN WORKS AS IT SHOULD!

Does this issue occur on a server? [yes/no]
no, this is a local game

If a (crash)log is relevant for this issue, link it here:

no crashlog, all works fine, only constructor does not work

[pastebin/gist/etc link here]

Show me your setup with some screenshots, including the Constructor GUI.

Dropping cobble works fine but when I switch to placing nothing happens...

I can place a block manually, but my constructor can not. Any hint welcome

dropping works img

with this config img

but placind does not work img

with this config img

placing a block manually there works img

That is weird. What I do know is that RS fires a block placement event, any external mod can block it, and then no blocks will be placed.

ty for checking. strange, I will try with RS only and report back...

Does it work if you place the Constructor somewhere else?

nope, nojoy. only going back to 1.24. then blocks get placed (but destructor still fails)

I will reduce mods and check if its a cross mod thing... I have mineconlonies relatively new. I will check and report

Ah, 1.2.4 didn't have the block placement event check yet. Later versions do.

1.2.4 did have the block removal event check, that explains why it won't remove even in 1.2.4.

tested my new save without 'minecolonies mod' and my old backup before I tested minecolinies and RS works just perfect!

Seems like 'minecolonies' does something to RS that break the place/break..

I will report it on their github. I think we can close this here. thanks for the superfast help and all the work you put into RS!

cheers

No problem! I wouldn't exactly say superfast, it took me 4 days to respond on this issue :-)

@raoulvdberge

Hmm, posted issue over at minecolonies github and got response...

I will try the config change and report...

There are two chances:

Disable colony protection in the config.
As we spoke with the forge team, fakePlayers should inherit the players UUID, I guess refinedStorage does that wrong

edit: disabling works. RS can place blocks again

minecolonies.cfg
...
# Enable the automatic colony protection?
B:enableColonyProtection=false
...

The fake player of RS can't inherit from the player, since there is no player data associated to a block.

Hmm, the block does not place itself but the constructor does. The constructor should have the UUID of the player that placed the constructor and then use it when placing a block. same with destructor, no?

I will check other block placers and how they behave in protected areas where only the allowed players are able to place or remove blocks...

Let me see if I can make RS blocks store the UUID of the placer.

just checked 'mechanical user' from extra utilities 2'... It CAN place blocks in the protected area of minecolonies...

picture

rightklick/place block/use upper left or random works both
config

maybe rwtema can help?

Gonna tag this as wontfix. I don't want to store any UUIDs in network nodes.