So this is not a concern if all settings are well chosen?
I do not see a left-over problem then.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Jan 12 2016
Looks very much like a sync issue, when switching between normal mode and creative mode, the server and client may have been in a different state, while you were in creative, the server may have registered you in "normal" mode, and thus the block you placed got reverted by the server as you did not have it in the inventory.
Duplicate of T371
Any more details on this?
you cannot pick up more than your inventory can hold.
Thus, you only pick up a limited amount, and the rest of the stack remains floating around, until the timer for dropped items to disappear removes it.
-Validated-
-confirmed-
Indeed, the typo is bad, however we left a note in the bug creation form for this:
Changing the selected version in the dropdown no longer triggers an immediate update, instead requiring you to manually click one of the update buttons (either in the build options window or the large orange [UPDATE] button in the lower corner of the launcher)
Increased default max-memory value for x64 from 1gb to 1.5gb
commit: 01e791ccd7e62034e7f4a9208eb4e2bd96320c78
Jan 11 2016
Get any ship with the old docking system, enter build mode, go to adv. and create docking. I am assuming that one should not be able to use rails while using the older system.
Here are the results thus far;
-Confirmed-
using shift to move faster in build mode causes this to be very easily reproduceable