Note the enigmatic tag. It's not meant to be clear what you're seeking.

• This was a trap. I'm a loser now :( – Wesley Situ May 27 '16 at 22:18

Partial:

Upper line

decodes through Morse code to:

EASTGOESNOONTONINE

Bottom line

is written with small hex numbers and reads: 800100003AB812A013B012A012B80000F2578574B7569554F557000000008001

Looking these 256 bits as 16x16 1-bit bitmap:

#..............#
................
..###.#.#.###...
...#..#.#.#.....
...#..###.##....
...#..#.#.#.....
...#..#.#.###...
................
####..#..#.#.###
#....#.#.###.#..
#.##.###.#.#.##.
#..#.#.#.#.#.#..
####.#.#.#.#.###
................
................
#..............#

i.e. THE GAME

Left line:

Rotated clockwise can be interpreted like morse too (with one error though, that's why this may be not the right way):
..... ...-- ..... .---- ..... ..... ....- .---- ..... ..--- ....- ..... ..... ...-- ..---
----- ....- ---.. ....- .---- ..... -.... ....- ..... ..--- ----- ....- ..--- ....-
----. ....- . ..--- ----- ....- .---- ..... ..--- ....- --... ..... ..... ....- .
.---. ....- . ....- --... ..--- . ..--- ----- ..... --... ....- ---.. ..... ----.
Decoded:
5351554152455320484156452042494E20415247554E#4E472E20574859 (# which is .---. is the error) Translated from hex to ascii shows:
SQUARES HAVE BIN ARGUN - before #
NG. WHY - after #
or thanks to @f'' comment:

SQUARES HAVE BIN ARGUING. WHY

Right line:

The string of digits (as transcribed here by @LeppyR64)
hes the following hex to ascii conversion:

CHAR THE WE

• Upper line is a correct translation. Bottom line is an accurate transcription. – Engineer Toast May 27 '16 at 19:24
• Master is on work computer so I can't double-check until Tuesday. However, the text is meant to read ARGUING. WHY – Engineer Toast May 28 '16 at 0:04
• @EngineerToast If the dot at the end of the third line and the dot at the start of the fourth line are combined into a dash, then it reads ARGUING as intended. – f'' May 28 '16 at 1:06
• Thanks for finding that, @f" I automated the process to make sure I didn't transpose anything but that's an issue I obviously overlooked. – Engineer Toast May 28 '16 at 3:11
• So the intent was to read the top line, right line, left line, then bottom line. I think I was a little too subtle with "News" (north, east, west, south). If you go in that order, each line helps you read the next. Also, that means that the bottom line is the last line and finding THE GAME message is the end, thus making you think about The Game and, consequently, lose The Game. You found the end but I didn't make it clear enough that you had... – Engineer Toast May 30 '16 at 19:52

Partial:

Right Line

Looks like a histogram. Read from top to bottom the values are:
4348415220544845205745

• Right line is an accurate transcription. – Engineer Toast May 27 '16 at 19:24
• Yeah, left is wrong, reworking it. – LeppyR64 May 27 '16 at 19:25