Trouble picking up water for non-ops

Maybe setting the spawn protection to 0 switches to the default value ?
What happened if you set the spawn protection to 1 ?

Changing the spawn protection value has no impact on the issue. I tried increasing the spawn protection to beyond the ~20 block area. The spawn protection works (can't break blocks) and the non-opped player can place the water source block successfully within that area - but still not within ~20 block area around the spawn point.

I discovered this issue when I was trying to use a water source block to hydrate a farm. The farm was within this ~20 block area. I dug a single block hole and right-clicked a full bucket on the hole. The water disappeared from the bucket but the hole didn't appear to get the water source block. Yet, as I mentioned earlier, right-clicking on the hole returned the water to the bucket as if it had been in the hole. The dirt around the hole with the 'invisible' water does not become hydrated.

Upon further investigation - although the bucket appears empty, the water is still in the bucket. So there is no 'invisible' water source block. Right-clicking a seemly empty bucket (after 'emptying' it within the ~20 block area) in an area beyond the ~20 block area will create a water source block.

Btw, I've been stating that this is a 20 block 'area'. It would probably be more correct to say 20 block radius. Unfortunately I can't determine if it's a circular area around spawn due to the spawn being on the edge of the tiny island.

I will try a different seed with the same parameters to confirm that this isn't simply an issue with my specific seed.

I tried this on another seed and got the same result. I could only place water source blocks from a bucket beyond a 20 block radius in 2 perpendicular directions and about 14 block in other directions. This is with spawn protection set to zero.

This is a screenshot of the area where a water source block can not be created from a bucket of water. The black wool near the center was my spawn. The yellow wool is the outer edge where water can not be placed. From the spawn point there are 18 blocks to the north, 17 to the east, 14 to the south, and 15 to the west.

This bug is very common among servers that have 'lag'. Some water collections and other block modifications or updates can take up to seven seconds or more to be relayed.

This lag can be caused by many things, including: 1. Advanced or excessive redstone- servers with excessive or advanced redstone can easily cause lag to all clients, especially on low-end computers. 2. A slow server- typical home computers generally do not make for very good servers when hosting more than 4 people, especially when a Minecraft client is running on the same system. Try running a server on a separate and idle computer, and using clients on different systems. 3. A slow internet connection- a slow internet connection or 'congested' traffic (several computers performing internet-intensive tasks simultaneously) can slow the performance of a server. This is also seen when an indirect connection or 'virtual LAN' (usually Hamachi) is used. In this connection, the server sends information to the remote server and is then processed. This information is then sorted and queued. After this, server information is authenticated and then routed to separate computers. This process can heavily slow down performance.

Even when lag is not experienced block updates can simply not be sent to the server. This is a bug and is sometimes experienced when breaking a sign. The text is already discarded before the server replaces the sign, leaving it empty.

This is not a case of lag. The client and server are connected by gigabit LAN. The server is a 3.2GHz dual core with 3GB of RAM. Minecraft is the only thing running on this server. I've replicated the bug on half a dozen different worlds. Posting that is this a case of 'lag' is counter-productive given the amount of detail I've posted here.

Can anyone else reproduce this bug? There are now 6 watchers of this bug - please comment if you can reproduce the same results I've described or comment if you CAN'T reproduce what I've described. Describe your testing procedures and I will try to replicate your results.

Thank you

Even without the presence of lag this bug is very common. As stated above, "Even when lag is not experienced block updates can simply not be sent to the server. This is a bug and is sometimes experienced when breaking a sign. The text is already discarded before the server replaces the sign, leaving it empty.". This is also experienced on SSP and is a block update issue. This bug has been tested several times in the past and numerous reports of it can be found on the internet.

Once again, it was not suggested that this was caused by lag, but simply stated that it is most commonly caused by lag.