Needs some more testing but the severe issues are gone. It's still possible from time to time where it seems to register a 180° flip but not sure yet how to reproduce that consistently.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Mar 29 2017
Mar 28 2017
Fix confirmed.
Picking up, and splitting into separate issues:
T2302: Starmote does not connect before joining the server directly
T2303: Starmote uplink breaks regular uplink
T2304: Starmotes newly added connections cannot be used until restarting it
T2305: Starmote search for entity interface not working
T2306: Starmote does not utilize the new blueprint categories
I think this issue has been fixed on the way and the report may be obsolete already.
-Validated-
Open for testing.
Well, there is a quite large range where you can see and connect blocks, but not see the purple boxes (for performance reasons).
Then there is a range, where you cant connect to, except with shift + v by going through a group recursive.
The idea is to prevent accidental links to blocks very far away and you may not even notice.
I set the block size you can set down at one time to being 100 length. I then set down 100 blocks attached to the core. I then set down a second set of 100. I ran along it checking with the yellow box to see if and where the blocks could be place about 20 or so blocks from the end the yellow box disappears and you can't connect any blocks to the power blocks that are visible.
Not actually a bug, but if they have constant inflow of blocks, its protected from being moved, as the race conditions could lead to blocks being destroyed or created.
While the first case would not be too much of a problem, the second case would be an exploit.
Can you still reproduce this? Or does it still happen?
I believe we fixed that issue or a related one, quite some time ago, but it may not cover this one directly.