Salem

anyone know what to do with the wet paper screen? :s

just leave it for 4 hours, you can then right click it to peal the dry paper off.

Mini Update #1
*Books should order their pages more accurately than before.
*Garlic Rabbit now appropriately uses game meats.
*Charred something now appropriately uses game meats.

JohnCarver wrote:*Players may now pave with Hay.

Makes it look like your base is paved with french fries!

Arkadion wrote:May I suggest that the last pavement placed is the one to overlap over the existing ones? So if I want brick over stone, I should pave first with stone, then with brick. In this case there will be no priority on any pavement.

You do realize that this would mean that every tile in the game would need to save when it was last changed?

loftar wrote:

Arkadion wrote:May I suggest that the last pavement placed is the one to overlap over the existing ones? So if I want brick over stone, I should pave first with stone, then with brick. In this case there will be no priority on any pavement.

You do realize that this would mean that every tile in the game would need to save when it was last changed?

MAKE IT SO

loftar wrote:

Arkadion wrote:May I suggest that the last pavement placed is the one to overlap over the existing ones? So if I want brick over stone, I should pave first with stone, then with brick. In this case there will be no priority on any pavement.

You do realize that this would mean that every tile in the game would need to save when it was last changed?

From what JC said, I understood that the pavements have some kind of 'priority' saved for each type. So that would mean you already save some data to order which pavement comes on top. One solution might be to save the time of change for each tile, as you say, meaning you would save the time instead of the priority (maybe more memory used). Also, you would save the time, only for the paved tiles, since the others are default (dropping dirt might be different).

I don't know how the code sees each tile, but I thought it would be something like this: all tiles are normal dirt((A); you pave with stone, the tile becomes stone-paved(B) (here it overlaps over the neighbouring dirt tiles); Paving with brick(C) a tile next to this, would make the latter overlap over the stone paved and the dirt tiles. This scenario would not need a time saved. As code, I think there will be a section to detect that you are paving with brick and you will change the sides of the tiles with that texture, instead of leaving the old stone part. I think you only depend on the material you just used for paving.

I think this would leave people the choice of how they want to pave, instead of always putting one specific pavement over another, creating a hierarchy (ex: brick over stone).

(I don't claim to know better than you, it was just my opinion and suggestion)

I'm pretty sure it would be possible to "override" this priority in a custom client

The thing suggested was that the last paved tile near a junction overlap the second to last paved one, which would involve the tiles remembering which was indeed paved last, or save junctions as they are created, either case pretty unnecessarily complicated as opposed to just having an order of priority

It all depends on how much freedom they want to give us: priority of materials means always getting the same results.