{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
publié à l'origine sous :BungieNetPlatform
2/28/2016 1:17:56 AM
4
Is it the crucible playbook slack? Still waiting for my invite lol
We made a slack bot that does this with our trials data, we would love to add it to that channel.
To answer your question try reading the wiki linked in the stickies thread here.
For reference on retrieving weapon perks look at our repo https://github.com/DestinyTrialsReport/DestinyTrialsReport
And recently DIM added weapon perks as well
English
-
Thats the one! I'm sure they'd want a DTR developer in there, hopefully they'll get back to you soon. Love your site btw. I'll look through your code for some help with retrieving perks. I found a pretty similar project that I'm basing mine off of: https://github.com/cprater/slack-destiny-bot
-
I'm very new to programming so please excuse my ignorance. I'm trying to set up this up but I'm having an issue getting it to run. I've got my bot going in slack but when running the slack-destiny-bot I'm getting the following error: /home/ubuntu/workspace/ghostbot/node_modules/slack-destiny-bot/src/bungie-data-helper.coffee is using deprecated documentation syntax { [Error: ENOENT: no such file or directory, open '.env'] errno: -2, code: 'ENOENT', syscall: 'open', path: '.env' } Any help would be greatly appreciated.
-
Modifié par pedroRVA : 3/3/2016 4:32:06 AMHah! I actually know exactly what this is because I encountered it myself. checkout the makeRequest function in the bungie.coffee file. That function expects an API key from the environment (like if you set it on your heroku instance) but this doesn’t work locally. To test locally, you can just substitute that line with “BUNGIE_API_KEY = <paste your api key>” In case its helpful, to expand on this, you generally don’t want to actually have your personal API key posted to your repo where someone else could see it, so thats why this sort of env variable is so useful.
-
That's the one we use too :)
