Version 1.1 (KartulUdus#13)

* Fix !register typo in dts example and docs (KartulUdus#8)

* Fix !register typo in dts example

* Update dts.md

* Minor text fixes (KartulUdus#10)

* RabbitMQ docs

* !track by Area Or distance, not both

* ⚠️DB migration! multi monster tracking, forms, raids tracking by level

* Configurable <amount> of messages per <seconds> limit for discord alarms

* Emoji fixes on all locales

* slight fix for {{form}}

* Rabbitmq.md where is admin panel

* Embed color by iv quality (KartulUdus#11)

* Support for embed color by perfection for IV alerts

* **Major** text fixes! Linting rules

* Catch and advise if Hastebin is down & send location data (only) to discord regardless

* Contributing guidelines, travis & PR|Issue templates

* Travis please

* Travis - broke eslint.json

* Travis build status to readme

* Docs update for 1.1 features

Author: KartulUdus

.eslintrc.json

@@ -0,0 +1,52 @@
+{
+  "parserOptions": { "ecmaVersion": 6 },
+  "extends": "airbnb-base",
+  "rules": {
+    // use tabs, not spaces, and in switch statements the case statement should indent again (the default is to be level with the switch)
+    "indent": [ "error", "tab", { "SwitchCase": 1 } ],
+    // if you want to put a blank line at the beginning or end of a block, knock yourself out
+    "padded-blocks": [ "off" ],
+    // i like tabs. besides, we set indent to require them
+    "no-tabs": [ "off" ],
+    // seriously, who cares if there's a blank line at the end of the file or not?
+    "eol-last": [ "off" ],
+    // sometimes having a long single line makes sense, this also seems buggy and inconsistent, so we ignore it
+    "max-len": [ "off" ],
+    // webstorm repeatedly tries to add it for us. it's easier not to fight it, even if it's not required.
+    "strict": [ "off" ],
+    // when setting the property of an object, you can specify the name even if it's unnecessary (ie: { foo: foo })
+    "object-shorthand": [ "off" ],
+    // unused vars are an error, except for function arguments.
+    // particularly with callbacks we may not use all the args, but we still like knowing they're available
+    "no-unused-vars": [ "error", { "vars": "all", "args": "none", "ignoreRestSiblings": true } ],
+    // you don't have to use operator assignment if you don't want to
+    "operator-assignment": [ "warn" ],
+    // we don't want else to be on the same line as the closing } of an if statement
+    "brace-style": [ "error", "stroustrup" ],
+    // if discord breaks because dangling commas, don't
+    "comma-dangle": ["error", "only-multiline"],
+    // it's possible that implicit coercion is not what you intended. webstorm warns about it, so should we
+    "no-implicit-coercion": [ "warn" ],
+    // if you wish to call all your errors err, go ahead
+    "no-shadow": ["error", { "allow": ["err"] }],
+    // if you're using 'this' somewhere that isn't a class you're probably doing something wrong
+    "no-invalid-this": [ "error" ],
+    // if you're not modifying the variable used in a loop condition, you've probably done something wrong...
+    "no-unmodified-loop-condition": [ "warn" ],
+    // don't use .call or .apply when you don't need to
+    "no-useless-call": [ "warn" ],
+    // forgetting to return after calling a callback is an easy mistake to make, so we'll warn you if you are
+    "callback-return": [ "warn" ],
+    // as we want to have dynamic translation files, dynamic require is needed
+    "import/no-dynamic-require": 0,
+    // reassigning and returning variables bad; however, \everything\ operator still requires it
+    "no-param-reassign": 0,
+    "no-return-assign": 0,
+    // to keep the cache continuous, the cache object has a dandling _ and needs it
+    "no-underscore-dangle": 0,
+    // geocoding backup to OSM on error is unhappy, make these separate and delete this rule please
+    "consistent-return": 0,
+    // because Travis-ci does not have config files, therefore this rule cannot error
+    "import/no-unresolved": 0
+  }
+}

.github/ISSUE_TEMPLATE.md

@@ -0,0 +1,31 @@
+<!--- Provide a general summary of the issue in the Title above -->
+
+## Expected Behavior
+<!--- If you're describing a bug, tell us what should happen -->
+<!--- If you're suggesting a change/improvement, tell us how it should work -->
+
+## Current Behavior
+<!--- If describing a bug, tell us what happens instead of the expected behavior -->
+<!--- If suggesting a change/improvement, explain the difference from current behavior -->
+
+## Possible Solution
+<!--- Not obligatory, but suggest a fix/reason for the bug, -->
+<!--- or ideas how to implement the addition or change -->
+
+## Steps to Reproduce (for bugs)
+<!--- Provide a link to a live example, or an unambiguous set of steps to -->
+<!--- reproduce this bug. Include code to reproduce, if relevant -->
+1.
+2.
+3.
+4.
+
+## Context
+<!--- How has this issue affected you? What are you trying to accomplish? -->
+<!--- Providing context helps us come up with a solution that is most useful in the real world -->
+
+## Your Environment
+<!--- Include as many relevant details about the environment you experienced the bug in -->
+* Version used:
+* Environment name and version (e.g. npm 5.6.0, nodejs v7.4.0):
+* Operating System

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,30 @@
+<!--- Provide a general summary of your changes in the Title above -->
+
+## Description
+<!--- Describe your changes in detail -->
+
+## Motivation and Context
+<!--- Why is this change required? What problem does it solve? -->
+<!--- If it fixes an open issue, please link to the issue here. -->
+
+## How Has This Been Tested?
+<!--- Please describe in detail how you tested your changes. -->
+<!--- Include details of your testing environment, and the tests you ran to -->
+<!--- see how your change affects other areas of the code, etc. -->
+
+## Screenshots (if appropriate):
+
+## Types of changes
+<!--- What types of changes does your code introduce? Put an `x` in all the boxes that apply: -->
+- [ ] Bug fix (non-breaking change which fixes an issue)
+- [ ] New feature (non-breaking change which adds functionality)
+- [ ] Breaking change (fix or feature that would cause existing functionality to change)
+
+## Checklist:
+<!--- Go over all the following points, and put an `x` in all the boxes that apply. -->
+<!--- If you're unsure about any of these, don't hesitate to ask. We're here to help! -->
+<!--  NOTE: In order to check code style locally and avoid having your build rejected by Travis, -->
+<!--  run the following commands before you commit: `npm run lint`. Fix anything it is unhappy about -->
+- [ ] My code follows the code style of this project.
+- [ ] My change requires a change to the documentation.
+- [ ] I have updated the documentation accordingly.

.travis.yml

@@ -0,0 +1,10 @@
+language: node_js
+node_js:
+  - "lts/*"
+
+cache:
+  directories:
+    - "node_modules"
+
+script:
+  - npm run lint

README.md

@@ -1,5 +1,6 @@
 ![logo](https://raw.githubusercontent.com/KartulUdus/PoracleJS/master/docs/_assets/PoracleJS.png)  
 
+[![Build Status](https://travis-ci.org/KartulUdus/PoracleJS.svg?branch=develop)](https://travis-ci.org/KartulUdus/PoracleJS)
 
 #### Introduction
 

app/src/discord/client.js

@@ -1,14 +1,14 @@
 const Discord = require('discord.js');
+
 const client = new Discord.Client();
 const config = require('config');
-const token = config.discord.token;
-const log = require("../logger");
+const log = require('../logger');
 
 module.exports =
 
 client.on('ready', () => {
-    log.info(`Discord botto "${client.user.tag}" ready for action!`);
-})
+	log.info(`Discord botto "${client.user.tag}" ready for action!`);
+});
 
-client.login(token);
+client.login(config.discord.token);