# Mashinky – Block Signals Guide

Block signals explained, with pictures.

## Basics

Hello. This is a short guide explaining the basic signals in the game Mashinky.

The signals divide your track into BLOCKS, that’s why we call them block signals. Their purpose is to prevent trains from one block entering into another block with a train in it. This prevents train crashes.

Let’s build a simple track.

This whole track is considered as a BLOCK. I will use colors to show BLOCKS:

If we add a signal, it will cut this block in half on that particular spot:

But since the left part and right part of the rail are connected by the other side, our rail is still connected as one BLOCK:

This means that if you add a train now, the signals will stay RED forever.

To split our rail into two BLOCKS, we need at least one more signal:

Now the game sees our rail as two BLOCKS, separated by our signals:

Now if you added one train, the train will be able to pass through the signals and circle around our rail.

By adding more signals, you can divide tracks into many BLOCKS.

## Crossings

Most common problems are caused by tracks crossing each other. Let’s have a look.

By adding tracks to a certain BLOCK, you extend it, like this:

However, when you cross another track, the BLOCKS of these tracks will merge together:

Our blue BLOCK is gone, because the tracks intersect.

It doesn’t matter that trains can never turn on this crossing. The game calculated, that in theory, there might come a situation when train A is on the crossing, and train B could enter the crossing, crashing into the train A. Therefore the game merges the blue block into the yellow block, to prevent this theoretical crash from ever happening.

But since you want this track to function, you need those blocks separated, right? So let’s add another signal:

Now we have separated the crossing from the rest of the the blue block and train can run again. This simple method – separating blocks – is used even in the most complex of crossing designs to make them function.

## Crossing Examples

Here are some examples of the simple crossings you can use:

Basic tracks

3-way tracks

4-way tracks

In our 3-way and 4-way example, we have used multiple signals on the turns, creating very small BLOCKS of rail. These actually serve no purpose, but I added them for this example to show how different BLOCKS form on different crossings.

These crossings are useful when you only run a small amount of trains through them. Only one train at a time can pass through the middle section and other trains have to wait. This becomes more apparent, if you start using two one-way rails:

The (purple) middle section now connects 8 different tracks, and all have to wait if a train is crossing. If you’re building a rail like this, or plan running many trains in the future, it will be better to separate the rails using a tunnel, or a bridge:

This should be enough for you to build whatever you need.
{"found_math": false, "script_math_tex": 0, "script_math_asciimath": 0, "math_annotations": 0, "math_alttext": 0, "mathml": 0, "mathjax_tag": 0, "mathjax_inline_tex": 0, "mathjax_display_tex": 0, "mathjax_asciimath": 0, "img_math": 0, "codecogs_latex": 0, "wp_latex": 0, "mimetex.cgi": 0, "/images/math/codecogs": 0, "mathtex.cgi": 0, "katex": 0, "math-container": 0, "wp-katex-eq": 0, "align": 0, "equation": 0, "x-ck12": 0, "texerror": 0, "url": "https://gameplay.tips/guides/1278-mashinky.html", "fetch_time": 1656555288000000000, "content_mime_type": "text/html", "warc_filename": "crawl-data/CC-MAIN-2022-27/segments/1656103646990.40/warc/CC-MAIN-20220630001553-20220630031553-00683.warc.gz", "warc_record_offset": 310312888, "warc_record_length": 42552, "token_count": 633, "char_count": 2973, "score": 3.546875, "int_score": 4, "crawl": "CC-MAIN-2022-27", "snapshot_type": "latest", "language": "en", "language_score": 0.9408596158027649, "file_path": "/sailhome/yjruan/project/latent-lm/data/processed/finemath-4plus/finemath-4plus/train-00036-of-00064.parquet"}