tera-discord-relay

Chat relay between a Discord channel and TERA /guild chat.

Setup

You'll need:

Node.js
Git
a Discord bot account
a TERA account

Discord

Bot Account

Create a new Discord app.
After app creation, click "Create a Bot User" on the application's setting screen. Make note of the bot ID and the token.
Invite the bot to your server by going to this link: https://discordapp.com/api/oauth2/authorize?client_id={{BOT_ID}}&scope=bot&permissions=0 (but replace {{BOT_ID}} with your bot's ID).

TERA

Join the desired guild on the desired character to use as the bot relay.
If you want the relay to be able to complete guild quests, give it a role and assign the appropriate permissions in game.

Installation

Open up a terminal window and go to a place where you want to put the bot files. Then run:

git clone [email protected]:kyoukaya/tera-discord-relay.git
cd tera-discord-relay
npm install

Configuration

You'll need to make two JSON configuration files: one for Discord and one for TERA. You can see an example for each in the config/config-sample.json of their respective directories. It is strongly recommended that you make a new file instead of changing the sample file.

Also note that in order for the rally notification to work for members in Discord, a @rally role must be created and assigned to those who want to receive the notification.

Discord

socket-name can be anything as long as it matches what you put in the TERA config.
token is the token you got from the setup section above.
server-id can be obtained by right-clicking on the Discord server and clicking on "Copy ID". If you don't see it, open Discord settings, head down to "Appearance", and tick on "Developer Mode".
channels:
- gchat channel ID can be obtained by right-clicking on the desired channel and clicking on "Copy ID".

TERA

host and port will come from your region's server list. You can get links to the servers from the caali-hackerman/tera-proxy repo.

Also, TERA has a few version numbers you might need to change for big patches. Open up tera/config/config.json and look for these:

patchVersion is usually the major and minor patch number put together. For instance, if you launch TERA, go to server select, and see "56.03.02 EN2" at the bottom, try setting patchVersion to 5603. If that doesn't work, try 9901.
protocolVersion is not so easy to check, but if you run tera-proxy it'll display the protocol version when you connect to it.
Alternatively you can log the C_LOGIN_ARBITER packet of an actual login with tera-proxy.

Running

You'll need to start up two terminals.

One for Discord:

cd path/to/tera-discord-relay/discord
node . config/your-config-file.json

And one for TERA:

cd path/to/tera-discord-relay/tera
node . config/your-config-file.json

It's recommended to run these on an infinite loop because failure conditions terminate the program. However, do note that the auth server will start rejecting logins if too many are performed in a short span of time.

Updating

To pull general updates for the Discord relay app:

cd path/to/tera-discord-relay
git pull
npm install

Every major version patch, TERA has some versioning info that needs changing. See the section above on TERA configuration for more info. To update tera-data, simply run:

npm install tera-proxy/tera-data

If the console is throwing up errors about certain packets not being defined, you may need to edit the (protocolVersion).map file and add them;

S_GUILD_QUEST_LIST
S_GUILD_APPLY_LIST

kyoukaya / tera-discord-relay Goto Github PK