BlueLine Games Wiki - User contributions [en]

Main Page

2016-05-26T14:10:04Z

Sean Colombo: /* Games */ we don't have many docs, so at least linked out to Steam pages for now.

'''Welcome to the BlueLine Games Wiki!'''

This wiki is all about BlueLine Games, the games it makes, and the community that loves to play them!

You can find out more about our titles, get in-depth help and strategy tips, and
interact with other members to find someone to play with online.

== Games ==
* [[Heximilate]] - HTML5, Pokki, Chrome App, Online
* [[Hive]] - Xbox 360, [http://store.steampowered.com/app/251210/ Steam] (PC: Windows/Mac/Linux)
* [[Khet]] - [http://store.steampowered.com/app/312720/ Steam] (PC: Windows/Mac/Linux)
* [[Reversi]] - [http://store.steampowered.com/app/307430 Steam] (PC: Windows/Mac/Linux)
* [[Chess|Simply Chess]] - [http://store.steampowered.com/app/312280/ Steam] (PC: Windows/Mac/Linux)
* [[Tatsu]] - [http://store.steampowered.com/app/445070/ Steam] (PC: Windows/Mac/Linux)

=== In progress: Not released yet ===
* ''[[Elsewhere]] - Omniplatform, Not Announced ;)''
* '''TBA: Next board game titles!'''

== Open Source ==
* [[Node Chat]]
* [http://bluelinegamestudios.com/posts/introducing-bluezebra-a-gpl-command-line-reversi-ai/ BlueZebra] - command-line Reversi AI.

== Other Software ==
BlueLine Game Studios has made software other than games (in order to help us make games) and that has been released as well.
* [https://burndownfortrello.com Burndown for Trello] - Burndown Charts (and many other Scrum/Agile charts) that have become the most popular 3rd-party Trello app in the world! We created this while making our first Xbox game, [[Hive]] and have been improving it for many years. Free and Premium plans are available.
* [https://roksten.com Röksten] - Translation management system. We created this system to help us translate our games (and keep those translations updated).

== Game-Jam Games ==
* [[10sTD]] - HTML5

Main Page

2016-05-26T14:05:06Z

Sean Colombo: +Tatsu, B4T, Röksten

'''Welcome to the BlueLine Games Wiki!'''

This wiki is all about BlueLine Games, the games it makes, and the community that loves to play them!

You can find out more about our titles, get in-depth help and strategy tips, and
interact with other members to find someone to play with online.

== Games ==
* [[Heximilate]] - HTML5, Pokki, Chrome App, Online
* [[Hive]] - Xbox 360, Steam (PC: Windows/Mac/Linux)
* [[Khet]] - Steam (PC: Windows/Mac/Linux)
* [[Reversi]] - Steam (PC: Windows/Mac/Linux)
* [[Chess|Simply Chess]] - Steam (PC: Windows/Mac/Linux)
* [[Tatsu]] - Steam (PC: Windows/Mac/Linux)

=== In progress: Not released yet ===
* ''[[Elsewhere]] - Omniplatform, Not Announced ;)''
* '''TBA: Next board game titles!'''

== Open Source ==
* [[Node Chat]]
* [http://bluelinegamestudios.com/posts/introducing-bluezebra-a-gpl-command-line-reversi-ai/ BlueZebra] - command-line Reversi AI.

== Other Software ==
BlueLine Game Studios has made software other than games (in order to help us make games) and that has been released as well.
* [https://burndownfortrello.com Burndown for Trello] - Burndown Charts (and many other Scrum/Agile charts) that have become the most popular 3rd-party Trello app in the world! We created this while making our first Xbox game, [[Hive]] and have been improving it for many years. Free and Premium plans are available.
* [https://roksten.com Röksten] - Translation management system. We created this system to help us translate our games (and keep those translations updated).

== Game-Jam Games ==
* [[10sTD]] - HTML5

Main Page

2016-01-16T21:48:37Z

Sean Colombo:

Main Page

2016-01-16T21:48:27Z

Sean Colombo: Testing ConfirmEdit

Main Page

2016-01-16T21:47:46Z

Sean Colombo:

Node Chat/Docs

2015-10-10T00:09:22Z

Sean Colombo:

'''TODO: CONVERT THIS!!! This is copy/pasted from the Wikia docs & I just removed any private info... still need to update all of the paths, etc. to be for the new project.''

== Where is the code ==
* Front-end: https://github.com/Wikia/app/tree/dev/extensions/wikia/Chat2
* Back-end: https://github.com/SeanColombo/chat

== What is the chat's datastore? ==
The chat uses redis for a datastore. Currently, none of the data stored in redis DB is critical. Therefore it is not needed to provide replication or backup.

==How I can change debugging level?==
You can you add commend line option loglevel=INFO and just start server with it. Or edit this file (/chat/server_config.js line 57), Possible levels of debugging: CRITICAL, ERROR, WARNING, NOTICE, INFO, DEBUG. After you changed file you need to restart server. IDEA: it would be nice to keep debugging level in txt file. The file would be read every 1min by nodejs. So we wouldn't need to restart server when we want to change debugging level.

==How to restart server==
"sudo killall node" Server will be started automatically by runit process or supervisor if it was started using either of those.

==I don't see any problem in log but chat is broken where else to look==
You can try to use [http://en.wikipedia.org/wiki/Ngrep ngrep ]. Example of ngrep usage:
sudo ngrep -d any port 80

==What are the responsibilities of the Web-site stack==
PHP stack's responsibilities: rendering of the chat.php page, server and instance selection and authorization. All messages and status exchange is handled by node.js server.

==Where are the chat configurations==
Chat is special case where configuration need to be shared between the web-app stack and the Chat server. In order to solve this problem we store configuration in a JSON file. JSON format is easy to ready by PHP and JaveScript. Github location of an example config file: https://github.com/SeanColombo/chat/ChatConfig_EXAMPLE.json

==How do Chat and the main website exchange information and is it safe==
The site and Chat provides to each other API methods. In order to prevent users from injecting unwanted data to Chat or MediaWiki We use ChatCommunicationToken for signing requests. Each installation of the chat server needs to have its own ChatCommunicationToken.
https://github.com/SeanColombo/chat/ChatConfig_EXAMPLE.json#L2

==How does authorization work==
[[file:Chat_author.png| thumb| 250px]]
* User accesses chat.php
* The site gets all needed user information and store them in object(user info object)
* The site generates KEY and stores "user info object" in memcached under the KEY
* The page is rendered with KEY(wgChatKey) as one of the JS vars.
* Client Java Script accesses node.js server with KEY.
* Node.js sends the query to the site with KEY through API protected with ChatCommunicationToken.
* If the KEY is correct media wiki answers with JSON containing "user object".
* Now node.js server knows if user is authorized to connect and what his privileges are.
==What is the network protocol between node.js and browser==
For message transportation we use popular lib [http://socket.io/ socket.io] The
library implements wrappers for 5 different underline technology: websocket, flashsocket, htmlfile, xhr-polling, jsonp-pollin. However for compatibility and simplification reasons we pick only one format: xhr-polling. You can find more information about this transportation technique http://en.wikipedia.org/wiki/Comet_(programming) search for: XMLHttpRequest long polling.

== Can I test chat in my local development environment ==
Yes, simply follow the [[Node Chat/Docs/Dev Setup|Dev Setup Instructions]].

== Chat-Bot ==
If you need a chat-bot to help you test some things, Wikia user Sactage made a ruby chat and put it on github: https://github.com/sactage/chatbot-rb

==How do emoticons work==
Emoticons are added during message rendering. Any wiki can define there own emoticons by editing mediawiki:emoticons article. Default icons are defined in: https://github.com/Wikia/app/blob/dev/extensions/wikia/Chat2/ChatDefaultEmoticons.i18n.php
'''TODO: This needs to be ported to perhaps be not-mediawiki-specific anymore, but in a way that allows the Wikia instance to continue to work as-is.'''

= Scaling =
== Failover ==
One way to allow for high-availability is to have a second stack (on a second machine) and failover to that second computer automatically.

[[File:Chat_infrastructure_simple_view.png|thumb|150px]] In case of failure of active stack, traffic can be switched to other stack.

==Why there are many instances of node.js on chat machines==
[[File:Chat_top_processes.png|thumb|150px]] One of the limitation of [http://nodejs.org/ node.js] is that its single threaded which means that we can't use the full power of modern multi core servers. In order to use the full advantage of multi-core CPUs we run more than one instance on each machine.

==How the load is split between instances of node.js==
We use a simple modulo operation, <code>instance_id = chat_room_id % number_of_instances</code>. The chat_room_id could be based on some listing you have, or it could be the id for a subdomain of your site, depending on how you use the system.

File:Chat top processes.png

2015-10-10T00:08:58Z

Sean Colombo:

File:Chat infrastructure simple view.png

2015-10-10T00:08:54Z

Sean Colombo:

File:Chat author.png

2015-10-10T00:08:50Z

Sean Colombo:

Hive/Help/Steam

2015-10-10T00:06:41Z

Sean Colombo: The referenced release has happened a LONG time ago (probably over a year ago at this point).

This page is meant to provide additional help for the things that aren't covered in the Rules popup in-game.

== Advanced Controls / Keyboard Shortcuts ==
{| class="wikitable"
! Keys
! Effect
|-
| '''Arrow keys''' or <br/>'''Middle click & drag'''
| Change camera angle. This angle will "stick" between games. If you prefer a 2D perspective, just shift the camera to be looking straight down and you shouldn't have to adjust it again.
|-
| '''Home'''
| Return the camera to its default position.
|-
| '''F1'''
| Open up Rules dialog during the game.
|-
| '''F2'''
| Cycles to the next tile-set. Tiles can either be 3D insects, Classic tiles, or Carbon tiles.
|-
| '''F11'''
| Toggle Full-screen mode.
|}

== Elo Ratings ==
"[http://en.wikipedia.org/wiki/Elo_rating_system Elo Ratings]" - the same rating system used to rate professional chess players - are now provided for players who play Hive online. Everyone starts out with an initial rating of 1200. As you beat players your rating goes up, if you lose it goes down. In the case of a draw, the higher-rated player will have their rating decrease and the lower rated player will increase their rating.

Players with a "P" suffix are still starting out, so they are "Provisionally" rated. Once a player has played '''15 games'''*or more, they are no-longer provisionally rated, and their scores are submitted to the [http://steamcommunity.com/stats/251210/leaderboards/323561 Steam Leaderboard].

Normally, some highly-rated players might be weary of playing against new players since a new player could show up with the default rating of 1200, but actually be a Hive Master. This is the whole point of having Provisional Ratings. All new players start out provisionally rated and these provisionally rated players will NOT affect your rating if you are done being provisionally rated. This should help make it easier for new players to get into the system because nobody has any risk from playing them.

Hive/Help/Steam

2015-10-10T00:06:03Z

Sean Colombo: Created page with "This page is meant to provide additional help for the things that aren't covered in the Rules popup in-game. == Advanced Controls / Keyboard Shortcuts == {| class="wikitable"..."

This page is meant to provide additional help for the things that aren't covered in the Rules popup in-game.

== Advanced Controls / Keyboard Shortcuts ==
{| class="wikitable"
! Keys
! Effect
|-
| '''Arrow keys''' or <br/>'''Middle click & drag'''
| Change camera angle. This angle will "stick" between games. If you prefer a 2D perspective, just shift the camera to be looking straight down and you shouldn't have to adjust it again.
|-
| '''Home'''
| Return the camera to its default position.
|-
| '''F1'''
| Open up Rules dialog during the game.
|-
| '''F2'''
| Cycles to the next tile-set. Tiles can either be 3D insects, Classic tiles, or Carbon tiles.
|-
| '''F11'''
| Toggle Full-screen mode.
|}

== Elo Ratings ==
"[http://en.wikipedia.org/wiki/Elo_rating_system Elo Ratings]" - the same rating system used to rate professional chess players - are now provided for players who play Hive online. Everyone starts out with an initial rating of 1200. As you beat players your rating goes up, if you lose it goes down. In the case of a draw, the higher-rated player will have their rating decrease and the lower rated player will increase their rating.

Players with a "P" suffix are still starting out, so they are "Provisionally" rated. Once a player has played '''30 games'''*or more, they are no-longer provisionally rated, and their scores are submitted to the [http://steamcommunity.com/stats/251210/leaderboards/323561 Steam Leaderboard].

Normally, some highly-rated players might be weary of playing against new players since a new player could show up with the default rating of 1200, but actually be a Hive Master. This is the whole point of having Provisional Ratings. All new players start out provisionally rated and these provisionally rated players will NOT affect your rating if you are done being provisionally rated. This should help make it easier for new players to get into the system because nobody has any risk from playing them.

*''Note: as of 6/14/2014, our next release will include a change to revise this to 15 games.''

Hive

2015-10-10T00:05:44Z

Sean Colombo: Created page with "'''TODO: This page needs work... lots and lots of work!''' == Further Reading == * 'Help' for Steam version"

'''TODO: This page needs work... lots and lots of work!'''

== Further Reading ==
* [[Hive/Help/Steam|'Help' for Steam version]]

File:KingMovement.png

2015-10-10T00:05:08Z

Sean Colombo:

File:Castling.png

2015-10-10T00:04:59Z

Sean Colombo:

File:QueenMovement.png

2015-10-10T00:04:51Z

Sean Colombo:

File:RookMovement.png

2015-10-10T00:04:47Z

Sean Colombo:

File:BishopMovement.png

2015-10-10T00:04:42Z

Sean Colombo:

File:KnightMovement.png

2015-10-10T00:04:36Z

Sean Colombo:

File:EnPassant.png

2015-10-10T00:04:20Z

Sean Colombo:

File:PawnMovementAndCapturing.png

2015-10-10T00:04:16Z

Sean Colombo:

File:PawnMovement Opening.png

2015-10-10T00:04:04Z

Sean Colombo:

File:InitialSetup.png

2015-10-10T00:03:54Z

Sean Colombo:

Chess/Rules

2015-10-10T00:01:18Z

Sean Colombo: /* Translations */ reparse

== Preamble ==
These rules are meant to be short and simple. Long-form rules can be found other places such as [https://en.wikipedia.org/wiki/Rules_of_chess Wikipedia] or [https://www.fide.com/component/handbook/?id=171&view=article FIDE]. These rules are also meant to be short enough to easily embed in our version of [http://store.steampowered.com/app/312280/ Chess on Steam].
=== License: Public Domain ===
'''NOTE: BlueLine Games is releasing these rules (including accompanying images) to the Public Domain so you can use them however you see fit! Print them out for a Chess club, include them in an insert with a Chess set you're selling on Etsy, put them in a computer game, whatever!'''

=== Translations ===
We appreciate any help we can get translating these into other languages, but please note that all translations here must be released to the Public Domain also, for consistency.

{{:Chess/Rules/Translations}}

= Rules =

== Object of Chess ==
The object of Chess is to put the opponent's King in "[[#Checkmate|checkmate]]". This means that you have a piece that can move to capture the King, and the opponent has no single move that can stop that threat.

== Basics ==
[[Image:InitialSetup.png|right]]
The game starts off with the pieces set up as in the picture. White moves first and may make any legal move (see [[#Movement|movement]] section below). Then Black moves, and the players alternate back and forth until the game is ended.

<div style='clear:both'></div>

== Capturing ==
If a piece is able to move in such a way that it can end up on an opponent's space, the player may make this move and the opponent's piece is "captured" (removed from the game). While it is often helpful to capture the opponent's pieces to make it easier to win, there are no specific points for capturing pieces and the ultimate goal is still to put the opponent's King in [[#checkmate|checkmate]].

== Movement ==
Each piece type has different movement abilities. In most cases, a piece can only move in a direct path and is blocked by other pieces in its way. The exception to this is the Knight which hops to its final position regardless of the pieces in the middle. No piece is allowed to move in such a way that it puts its own King into "Check", and if a player is in Check, they must make a move which gets them out of Check if that is possible (if it's not possible then the Check was actually [[#Checkmate|Checkmate]]).

You may not move through your own pieces.

=== Pawn ===
[[Image:PawnMovement_Opening.png|right]]
[[Image:PawnMovementAndCapturing.png|right]]
The pawn is the only piece whose Movement and Capturing are different from each other.

==== Pawn Movement ====
On each pawn's first move, it has the choice to move either 1 space forward or 2 spaces forward (but cannot jump over or attack other pieces if there is something in the way). After its first move, each pawn may only advance one square forward at a time. The pawn is NOT allowed to capture pieces that are directly in front of it.
==== Pawn Capturing ====
A pawn can capture only by moving one space forward and to the left, or one space forward and to the right.
<div style='clear:both'></div>
==== Pawn: En Passant ====
[[Image:EnPassant.png|right]]
There is a special case where pawns may capture even if there is no piece on the space they're attacking. This is to simulate a pawn attacking the opponent while it was "in passing" going by. This case only applies when all of these conditions are met:
# On the move right before this, the other player moved their pawn forward two spaces.
# The pawn that just moved and the pawn that are about to attack must now be in the same row, and must be next to each other.
If these conditions are met, the attacking pawn can now move diagonally forward and towards the side of the victim (leaving it on the spot behind the victim, which it just passed) and then the victim piece is captured.
==== Pawn Promotion ====
If a pawn advances all the way to the other side of the board, as soon as it reaches the last row its player upgrades it to any of the four following pieces: Queen, Knight, Rook, Bishop. It is entirely up to the player that will get the new piece, so people usually choose a Queen.

<div style='clear:both'></div>

=== Knight ===
[[Image:KnightMovement.png|right]]
Knights move and capture by going exactly two spaces in any direction, then one space at a right angle from that (making an "L" shape). This can be done regardless of whether there are pieces in between its original location and its destination. This gives the Knight the privilege of being the only piece that can "jump over" other pieces. If there is an enemy piece at its destination, the Knight captures that piece.
<div style='clear:both'></div>

=== Bishop ===
[[Image:BishopMovement.png|right]]
The Bishop can move diagonally as many spaces as desired until it runs into another piece or the edge of the board. If it can move to a space occupied by an enemy piece, it can capture that piece.
<div style='clear:both'></div>

=== Rook ===
[[Image:RookMovement.png|right]]
The Rook can move in a straight line (not diagonally) as many spaces as desired until it runs into another piece or the edge of the board. If it can move to a space occupied by an enemy piece, it can capture that piece.
<div style='clear:both'></div>

=== Queen ===
[[Image:QueenMovement.png|right]]
The Queen can move diagonally or in a straight line as many spaces as desired until it runs into another piece or the edge of the board. If it can move to a space occupied by an enemy piece, it can capture that piece.
<div style='clear:both'></div>

=== King ===
[[Image:KingMovement.png|right]]
The King can move exactly one space in any direction and similarly, captures an enemy piece if there is one at its destination. The only exception to the King moving one space is when it "[[#Castling|Castles]]".
<div style='clear:both'></div>

=== Castling ===
[[Image:Castling.png|right]]
There is a special move called Castling which allows the King to move two spaces towards a Rook and for the Rook to swap to the other side of the King, all in the same move. This is only allowed if all of the following conditions are met:
* Neither the King nor this Rook have moved during this game.
* There are no pieces between the King and the Rook
* The King may not Castle out of check, it may not move past a space that would put it in Check, and it cannot move to a destination that would put it in Check (the Rook is allowed to be in danger at any point).
<div style='clear:both'></div>

== End Game ==
There are several ways to end a game. By far the most common are Checkmate and Stalemate. Some of these definitions rely on the term "Check": A King is said to be in Check when there is an opposing piece which would be able to capture the King on its next move if nothing was done to prevent that.
=== Checkmate ===
If a King is in Check and there are no moves for that King or any of his army to get him out of Check (even by capturing the threatening piece or putting themselves in danger) then this is a Checkmate and the player whose turn it is (who is unable to protect their King) loses.

=== Stalemate ===
If a King is NOT in Check and there are no moves for the King or any of his army that do not put him INTO Check, then this is a Stalemate (which is a type of Draw).

=== Threefold Repetition ===
If the same board position is repeated three times, then either player may declare the game a Draw before the next turn happens. If another move is made without either player declaring a Draw, and the game is no longer in a position that has been repeated three or more times, then the opportunity has passed. The opportunity can come up again if the game yet-again goes into a position that has occurred three or more times (even if it's the same position where nobody declared a Draw previously).

=== Insufficient Material ===
As pieces get captured and there are less and less pieces on the board, it is possible to get to a state where the remaining pieces are insufficient to allow either player to force the other one into Checkmate. In this case, the game is automatically declared a draw.

=== 50 Move Rule ===
If players make 50 different turns (25 each) without any pawn being moved or any piece being captured, then the game isn't making progress. In this case either player is allowed to call a Draw.

=== Resignation ===
Either player is allowed to Resign at any point. This counts as a Loss for that player.

=== Draw by Agreement ===
At any point, one player can propose a Draw. If the other player agrees, the game is counted as a Draw.

Chess/Rules/Translations

2015-10-09T23:57:11Z

Sean Colombo: Created page with "<noinclude> '''← back to Chess/Rules'''<br/> This page will be transcluded onto each translation (so it will only need to be updated in one spot... here). Rules: *..."

<noinclude>
'''← back to [[Chess/Rules]]'''<br/>

This page will be transcluded onto each translation (so it will only need to be updated in one spot... here).

Rules:
* The name of the language should be in THAT language (eg: "English" for English, "Deutch" for German).
* The languages should be listed alphabetically by their name.
* The actual page-name in the link should be the two-letter '''[https://en.wikipedia.org/wiki/List_of_ISO_639-1_codes ISO-639-1 language code]'''.

</noinclude>[[Chess/Rules/de|Deutch (de)]], [[Chess/Rules|English (en)]], [[Chess/Rules/es|Español (es)]], [[Chess/Rules/fr|Français (fr)]], [[Chess/Rules/sv|Svenska (sv)]] (''[[Chess/Rules/Translations|add more]]'')

Chess/Rules

2015-10-09T23:56:26Z

Sean Colombo: Created page with "== Preamble == These rules are meant to be short and simple. Long-form rules can be found other places such as [https://en.wikipedia.org/wiki/Rules_of_chess Wikipedia] or [htt..."

Chess

2015-10-09T23:55:31Z

Sean Colombo: Created page with " * Chess/Rules"

* [[Chess/Rules]]

Node Chat/Docs/Dev Setup

2015-10-09T23:54:45Z

Sean Colombo: Pulled over from prior version of wiki

← [[Node Chat]] / [[Node Chat/Docs|Docs]]

== Overview ==
The full stack of chat will run on the devboxes if you enable the extension.

== Setup ==
To set it up:

* Check out the chat repo to <code>/usr/wikia/source/chat</code>:

git clone https://github.com/SeanColombo/chat

* Edit config/ChatConfig_EXAMPLE.json (and rename it not to have _EXAMPLE in it)) and
** update <code>"ChatHost": "dev-chat:8080"</code> to <code>"ChatHost": "dev-chat:9002"</code>
** change all instances of <code>dev-chat</code> to <code>dev-YOURDEVBOX</code>
* Add to <code>DevBoxSettings.php</code>: <code>$wgEnableChat = true;</code>
* Install Redis if not already on your dev-box:

sudo apt-get install redis-server

* Make sure redis-server is running locally

service redis-server start

* run npm install inside the chat main directory

npm install

== Running Chat ==

* start the chat service
cd [PATH TO THE github CHECKOUT]
/usr/bin/node server.js loglevel=debug mode=dev basket=1 instance=2

== Running Chat with multiple baskets ==
If you need to test failover between the multiple baskets, then you can make that happen on dev:
* Modify <tt>[github clone location]/ChatConfig.json</tt> to have multiple buckets for dev. For example, change the code to:
<pre>
"dev":{
"ChatHost": "dev-chat:9000",
"MainChatServers": {
"1":[ "dev-chat:9001" , "dev-chat:9002" ],
"2":[ "dev-chat:9003" , "dev-chat:9004" ]
},
"ApiChatServers": {
"1":[ "dev-chat:9101", "dev-chat:9102" ],
"2":[ "dev-chat:9103", "dev-chat:9104" ]
},
"RedisServer": {
"1": "127.0.0.1:6379",
"2": "127.0.0.1:6379"
},
"ProxyServer": "127.0.0.1:6081"
},
</pre>
But with your whatever your chat server box is, instead of dev-chat.
cd /usr/wikia/source/chat
/usr/bin/node server.js loglevel=debug mode=dev basket=1 instance=2
/usr/bin/node server.js loglevel=debug mode=dev basket=2 instance=2

* You can move all wikis over to use a different basket by changing wgChatServerBasket in WikiFactory for community.wikia.com to put it in a different basket (all wikis share the setting from Community). - '''TODO:Update this'''

== Testing multiple instances ==
''' TODO: CHAT PROXY NOTES HERE... need to make some general-purpose proxy rules to keep Chat servers only internally accessible.'''

== Troubleshooting ==

If you get an error on the AJAX request that says:

io.j[0](new Error("handshake unauthorized"))

It means that the chat server has probably allocated an instance of the chat for that wiki on somebody else's devbox. Try using a different test wiki. If that doesn't work, flush redis cache to reset all chat rooms, then try again:

$ redis-cli
> flushall

== Additional Help ==

* Contact the Social Team to debug if anything goes wrong (it probably will)
* If the client can't connect, double check the instance number in the http request, it might be 1
* Contact Owen if you want to set up a full hproxy config for this to run both instances.

Node Chat/Docs

2015-10-09T23:54:14Z

Sean Colombo: Pulling over page from prior version of wiki (which got spammed)

Node Chat

2015-10-09T23:52:44Z

Sean Colombo: Created page with "TODO: THINK OF A NAME FOR THE PROJECT! Maybe even get a logo. That'd be cool. == History == While working at Wikia, I made a node.js Chat server that integrated with Wikia (M..."

TODO: THINK OF A NAME FOR THE PROJECT! Maybe even get a logo. That'd be cool.

== History ==
While working at Wikia, I made a node.js Chat server that integrated with Wikia (MediaWiki) accounts. Since [http://wikia.com Wikia] code is open source, I forked the [https://github.com/Wikia/chat original code] and (keeping the same MIT license) started making the chat-code general purpose while building [[Elsewhere]].

Wikia is one of the most popular sites in the United States ([https://www.quantcast.com/top-sites currently #16], right below Wikipedia) so the server has already had the chance to be put under serious stress-testing and has been incrementally improved over the years since it was released.

== Goals ==
* Make a highly scalable node chat server that can be plugged into existing sites.
* Continue using each site's authentication systems so that the users don't have to log in to chat separately.
* Make it easy to configure a new site to use this server (1 hour setup maximum).
* Reorganize the code so that everything site-specific can be easily configured & get both Wikia and [[Elsewhere]] to run on this.
* Keep the latest stable version of the project running on both Wikia and Elsewhere.

== Documentation ==
These might need to be merged. These are the docs from Wikia:
[[Node Chat/Docs]]

== Code & License ==
The code on Github and is [https://github.com/SeanColombo/chat/blob/master/LICENSE licensed under the MIT License].

=== Backend ===
* GITHUB REPO: https://github.com/SeanColombo/chat
* To run the server: <tt>node server.js mode=dev basket=1 instance=1 loglevel=debug</tt>

=== Frontend ===
When you have the node.js server running, you will probably want need some front-end website code to put widgets on your site which point your users to the chat, and you'll need some code to let the chat server authenticate the user using your site's auth system.

We don't have a good generalized front-end example yet... but here's the front-end Wikia code for reference:<br/>
https://github.com/Wikia/app/tree/dev/extensions/wikia/Chat2

'''TODO: Add some default front-end code in a directory in the main github repo. This will be unused by most actual installations, but they can copy/paste it to the right spot in their own projects.'''

=== Integration ===
'''TODO: Instructions on how to check this project out in a way that you can use the same Model javascript between your site and node servers.'''

=== Setup ===
THESE INSTRUCTIONS WILL NEED A LOT OF WORK!
# git clone the [https://github.com/SeanColombo/chat Respository] to where you want the code to go (and create a branch if you want to modify the code... you can always do that later if you are unsure).
# OPTIONAL: set the WIKIA_CONFIG_ROOT environment variable to a directory where your config will be (by default, the config is in the root directory).
# Copy the ChatConfig_EXAMPLE.json to ChatConfig.json and update it with reasonable settings (eg: everything localhost to start with).
#
# run "node server.js" and fix bugs until it works ;) as I'm doing that I'll be filling in this "Setup" list and making Cleanup tasks below.

== Refactoring Needed ==
This section will be for tracking the changes needed to make the Wikia/MediaWiki system able to be used generally on other sites (while still running cleanly on Wikia).
# Make the process.env.WIKIA_CONFIG_ROOT not have the word Wikia in it (maybe fall back to the Wikia version so that we don't have to update the env on the Wikia chat servers to work with the new code).
# Make installer-script which will create the default ChatConfig.json and if someone tries to run the server when that json file doesn't exist, instruct them to run the install script. Install script should ask for settings (but have defaults for all of them) and do a reasonably cryptographically-secure job of generating the secret code (otherwise someone can attack the server based on knowing what day the chat server went live & trying all of the seconds).
# Add some project-branding somewhere which is on by default (but probably set it to be turned off on Wikia... ask them about that).
# In Wikia, delete Chat2/docs/chat.sql for cleanliness (it's just the schema for the little PHP prototype we made)
# Refactor WMBridge to be SiteBridge and mwBridge to be siteBridge in Chat (WMBridge sounds like some dyslexia anyway). For Wikia's distribution, have it be MwSiteBridge (and just a swapped require() call to get that instead of the default SiteBridge).
# Need to make the NodeApiClient more general (eg: not MediaWiki specific) and should make the name of that and the nodeInterface more obvious so it's clear that the client talks to the node server's API where as the nodeInterface answers questions FROM the server.
# ChatConfig.json is duplicated! We have one in /node/ChatConfig.json and one in /public_html/NodeChat/ChatConfig.json... make one of these able to be read by both node and PHP. When there are two, they have to be kept in sync which is bad bad bad.
# ChatHost
## Right now, it's not documented, but the frontend ALWAYS connects to ChatHost. This is a security feature so that only 1 port has to be open on the chat servers & we can easily add chat instances without reconfiguring the firewall. There is some haproxy config on the ChatHost that redirects to the appropriate ports based on rules. Document this. Example dev-box rules are in <tt>PRIVATE/Cloud Servers/chat_haproxy_example.txt</tt>
## haproxy isn't easy in Windows, so I just set the ChatHost port to be the same as Instance 1, so there really is only 1 working instance possible on Windows devboxes right now.
## Ideally, we could make a way to do the rewriting on windows devboxes also... in the meantime we need to make it clear that Windows devboxes only do one instance.

Main Page

2015-10-09T23:52:26Z

Sean Colombo: Pulling pages over from the prior wiki (which had gotten spammed beyond repair).

User:Sean Colombo

2015-10-09T23:52:02Z

Sean Colombo: Created page with "== About Me == I founded BlueLine Games in 2011 and we have been bringing digital versions of award-winning table top games to several platforms - Xbox 360,..."

== About Me ==
I founded [[BlueLine:About|BlueLine Games]] in 2011 and we have been bringing digital versions of award-winning table top games to several platforms - Xbox 360, HTML5, Steam (PC/Mac/Linux) - since then! :D

== Find Me, Elsewhere ==
* [https://twitter.com/seancolombo @seancolombo] on twitter
* [https://twitter.com/bluelinegames @bluelinegames] on twitter