Post / Recent Updates!

Hello, and welcome back to another post on YATM. There is a lot to cover, and because I'm lazy, there will be no screenhots this round. For now at least. Since I forgot to note the changes down, I'll be going by the github changelog and explain everything that's happened since the Big Data Update.

New Formspec backgrounds

YATM has a slew of new formspec backgrounds, comes in 2 different formats to support older clients that didn't have 9-slice background support. Granted it works sometimes, and other times it straight up shows a black background, I have no idea why.

Data to Mesecon bugfix

The Data to Mesecon node had a serious bug where it would emit a data event. For those who don't know what this node does, it takes a data event and then outputs a mesecon signal. That's it, it shouldn't be emitting data.

Data Switcher

Texture Atlas(es)

Model

Data Frame Motors are now implemented

While the motors existed from the beginning, they couldn't actually be operated since the data network system wasn't implemented yet. But that has changed, Data Frame Motors can now be operated!

Data Frame Motor

Texture Atlas(es)

Model

Machines can now use a function for their capacity

More of a development side thing, even machine using the 'devices' API can now specify a function that returns their energy capacity.

Thermal code gets a slight revamp

While still a glorious WIP, the thermal system has seen a quick revisit, and nodes that use the system have also seen a slight revamp as well.

Heat spreads over thermal ducts, and unlike energy, it isn't 'consumed', but rather just used until the source is unable to keep the duct heated.

Thermal Duct

Texture Atlas(es)

Model

Thermal Node

Texture Atlas(es)

Model

Codex has it's first few entries and demos!

The CODEX has seen some work, and while it's interface is still atrociously bad, it has begun accomplishing it's intended task: Providing much needed documentation pages on various YATM nodes!

CODEX

Texture Atlas(es)

CODEX [Deployment Mode]

Texture Atlas(es)

Quarry walls no longer drop quarries when broken

A rather interesting copy-paste mistake, Quarry walls when broken, would drop Quarries instead of the wall.

Quarry Wall

Texture Atlas(es)

Model

Reactors now send a chat message to the player that started it

Debugging a misbehaving reactor is hard, so with a bit of help, reactors will now send a message to the player that started or stopped it providing some feedback.

More improvements are needed in this department however.

Reactors replacing nodes on start/stop

A rather terrible bug was found where a reactor would incorrectly replace nodes when started or stopped, this was due to a stale node record stored in the reactor cluster.

Since this bug could potentially plague other systems, YATM now pulls the latest node information when necessary instead of relying on it's stale record.

The stale record is kept mostly for debugging and for cases where the original node cannot be accessed (i.e. the block is unloaded)

DSCS takes it's first baby steps with working drives.

So the DSCS can now store items in it's drives, fluids are still a work in progress and the elemental system is no where in sight!

It's still buggy and may lose items, plus the format is still in flux.

With semi-working drives in place, 2 new nodes were added as well, the Materializer and Digitizer, these nodes will take or add items/fluids/anything-else to or remove from the DSCS system respectively.

Drive Case

Texture Atlas(es)

Model

Digitizer

Texture Atlas(es)

Model

Materializer

Texture Atlas(es)

Model

Load and Unload hooks for nodes in clusters

One issue encountered in the DSCS system was the loading and unloading of nodes with externally controlled resoucres (i.e. Fluid Inventories for drives).

The cluster system will now call a node's unload or load hook in it's specified network or system.

Granted, I have encountered cases where the unload isn't called when I expected it, but some time after. This is due to the block unloading code being a bit slow to act.

Energy cells finally have their correct animation

Did you know, energy cells were suppose to have a pulsing animation? No? Well they were, but due to some... issues, they were played straight instead of ping-pong, this has been finally rectified.

Energy Cell (basic)

Texture Atlas(es)

Model

Energy Cell (normal)

Texture Atlas(es)

Model

Energy Cell (dense)

Texture Atlas(es)

Model

Energy Cell (basic) [Creative]

Texture Atlas(es)

Model

Energy Cell (normal) [Creative]

Texture Atlas(es)

Model

Energy Cell (dense) [Creative]

Texture Atlas(es)

Model

Devices Cluster is now uses Simple Cluster implementation

A bit of code refactoring, the devices cluster was a special snowflake due to it's additional requirements of changing some nodes depending on an overall controller state. It still maintains it's special status, but with less code now, as it has been refactored to work with the Simple Cluster base system, so no more odd bugs between the different implementations.

New Carbon Steel nodes

Being badgered again to add more carbon steel textures, I have recycled the machine panels to provide new variants.

Carbon Steel Base Panel Block

Texture Atlas(es)

Model

Carbon Steel Plain Panel Block

Texture Atlas(es)

Model

Carbon Steel Smooth Block

Texture Atlas(es)

Model

Mesecon Locks have new textures

To say the least, I despised the old textures, and I still despise the new ones.

I'm just not sure how I want them to look...

Mesecon Lock (Black)

Mesecon Lock (Blue)

Mesecon Lock (Brown)

Mesecon Lock (Cyan)

Mesecon Lock (Dark Green)

Mesecon Lock (Dark Grey)

Mesecon Lock (Green)

Mesecon Lock (Grey)

Mesecon Lock (Light Blue)

Mesecon Lock (Magenta)

Mesecon Lock (Orange)

Mesecon Lock (Pink)

Mesecon Lock (Red)

Mesecon Lock (Violet)

Mesecon Lock (White)

Mesecon Lock (Yellow)

Texture Atlas(es)

Model

ICBMs

YATM Armoury has seen a new module, the ICBM module, while seriously a WIP, it combines the destructive nature of the Armoury module with the control systems from data to unleash a block of metal on your enemies.

If you do manage to launch an ICBM, don't expect an explosion, but at least expect a hilariously bad flight code.

ICBM Silo

Texture Atlas(es)

Model

ICBM Guiding Ring (Double Band)

Texture Atlas(es)

Model

ICBM Guiding Ring (Single Band)

Texture Atlas(es)

Model

ICBM Guiding Ring [Warning Strips] (Double Band)

Texture Atlas(es)

Model

ICBM Guiding Ring [Warning Strips] (Single Band)

Texture Atlas(es)

Model

Data Control Plane

A challenge poised by the ICBM was the need to set multiple variables over the data interface.

While this could be somewhat accomplished easily by the computers (eh em, they still aren't implemented fully), there needed to be a stop gap in the meantime.

The control plane allows players to install various components into the node and then attach the usual data configurations to each component, so you can trigger multiple data events in the same node.

Data Control Plane [2x2]

Data Control Plane [4x4]

Data Control Plane [8x8]

Texture Atlas(es)

Model

Control Button [Momentary Button] (Black)

Control Button [Momentary Button] (Blue)

Control Button [Momentary Button] (Brown)

Control Button [Momentary Button] (Cyan)

Control Button [Momentary Button] (Dark Green)

Control Button [Momentary Button] (Dark Grey)

Control Button [Momentary Button] (Default)

Control Button [Momentary Button] (Green)

Control Button [Momentary Button] (Grey)

Control Button [Momentary Button] (Light Blue)

Control Button [Momentary Button] (Magenta)

Control Button [Momentary Button] (Orange)

Control Button [Momentary Button] (Pink)

Control Button [Momentary Button] (Red)

Control Button [Momentary Button] (Violet)

Control Button [Momentary Button] (White)

Control Button [Momentary Button] (Yellow)

Texture Atlas(es)

Control Switch (Black)

Control Switch (Blue)

Control Switch (Brown)

Control Switch (Cyan)

Control Switch (Dark Green)

Control Switch (Dark Grey)

Control Switch (Default)

Control Switch (Green)

Control Switch (Grey)

Control Switch (Light Blue)

Control Switch (Magenta)

Control Switch (Orange)

Control Switch (Pink)

Control Switch (Red)

Control Switch (Violet)

Control Switch (White)

Control Switch (Yellow)

Texture Atlas(es)

Plenty of new Motor Frames

Motor frames now have more frame variants, and wire frames finally do something.

Motor frames come in variants of 1-6 faces with sticky or wired or both.

Sticky Frame (All Faces)

Texture Atlas(es)

Model

Sticky Frame (Axle)

Texture Atlas(es)

Model

Sticky Frame (Cross Axle)

Texture Atlas(es)

Model

Sticky Frame (Five Faces)

Texture Atlas(es)

Model

Sticky Frame (Four Faces)

Texture Atlas(es)

Model

Sticky Frame (One Face)

Texture Atlas(es)

Model

Sticky Frame (Three Faces)

Texture Atlas(es)

Model

Sticky Frame (Two Faces)

Texture Atlas(es)

Model

Wire Frame (All Faces)

Texture Atlas(es)

Model

Wire Frame (One Face)

Texture Atlas(es)

Model

Wire Frame (Wire & Sticky Axle)

Texture Atlas(es)

Model

Wire Frame (Wire & Sticky Cross Axle 1)

Texture Atlas(es)

Model

Wire Frame (Wire & Sticky Cross Axle 2)

Texture Atlas(es)

Model

Wire Frame (Wire Axle)

Texture Atlas(es)

Model

Wall Mounted Data Cables

Placing cables on the ground gets boring after a while, sometimes you want to place them on the wall, but due to their implementation, they couldn't be rotated to lay flat on the wall, leading some some... horrendous looking connections.

As of such, and painfully as such, a set of new cables were added that can be manually rotated, regular cables will continue to exist.

Don't mind the textures if they all look the same, in minetest the cables have different models, so parts of the texture are omitted.