The bot is still using the Ixalan rules documents.

The command "!card Nix" finds a random Phoenix instead of the card Nix.

Ideas to solve this:

• If the bot finds multiple results, interpose a text comparison before the result is posted and if one card matches the query exactly, post that one.
• Prioritize results that start with the search query if no card matches it exactly.
• Prioritize results that contain the search query as a solitary word instead of a part of a word (Nix in Phoenix).

Would it be at all possible to create a feature in which you could change the prefix of the commands from ! to another symbol?

I run a small community that uses a fair number of bots and I would like to be able to tweak the prefixes of them so that they don't overlap.

!docs (or documents)
will display the important docs ipg, mtr AND also like PPTQ requierments or GPT requierments for even a storeowner so any judge can easy find it.
(i just had to search it so this idea came to me :P )

!Judge location
Shows you judge in a certain location and if the judge is in the chat highlights him?

!judge level
If you search for a certain level.

It would be nice to have the option to know the foil price as well. I thought of doing it with "!price isolate is:foil" to narrow down the result, but that doesn't work

Some Paragraphs in the CR are basically just headlines (ie 702.15 Lifelink) currently the bot just responds 702.15 Lifelink to a query for 702.15.

A result like:

702.15 Lifelink
702.15a Lifelink is a static ability.
Further subsections are 702.15b - 702.15f

would be much more useful.

!help
shows what the bot can do. all the possible commands and stuff :D

which will break the !standard command

2017-04-12T09:53:27.205351+00:00 app[bot.1]: [2017-04-12 09:53:27.192] [ERROR] bot - An error occured while handling !cr 510.1c :
2017-04-12T09:53:27.205355+00:00 app[bot.1]:  { Error: Bad Request
2017-04-12T09:53:27.205356+00:00 app[bot.1]:     at Request.callback (/app/node_modules/superagent/lib/node/index.js:626:17)
2017-04-12T09:53:27.205357+00:00 app[bot.1]:     at /app/node_modules/superagent/lib/node/index.js:795:18
2017-04-12T09:53:27.205357+00:00 app[bot.1]:     at IncomingMessage.<anonymous> (/app/node_modules/superagent/lib/node/parsers/json.js:16:7)
2017-04-12T09:53:27.205358+00:00 app[bot.1]:     at emitNone (events.js:91:20)
2017-04-12T09:53:27.205359+00:00 app[bot.1]:     at IncomingMessage.emit (events.js:185:7)
2017-04-12T09:53:27.205359+00:00 app[bot.1]:     at endReadableNT (_stream_readable.js:974:12)
2017-04-12T09:53:27.205360+00:00 app[bot.1]:     at _combinedTickCallback (internal/process/next_tick.js:74:11)
2017-04-12T09:53:27.205361+00:00 app[bot.1]:     at process._tickCallback (internal/process/next_tick.js:98:9)
2017-04-12T09:53:27.205361+00:00 app[bot.1]:   original: null,
2017-04-12T09:53:27.205362+00:00 app[bot.1]:   response:
2017-04-12T09:53:27.205363+00:00 app[bot.1]:    Response {
2017-04-12T09:53:27.205363+00:00 app[bot.1]:      domain: null,
2017-04-12T09:53:27.205364+00:00 app[bot.1]:      _events: {},
2017-04-12T09:53:27.205364+00:00 app[bot.1]:      _eventsCount: 0,
2017-04-12T09:53:27.205365+00:00 app[bot.1]:      _maxListeners: undefined,
2017-04-12T09:53:27.205366+00:00 app[bot.1]:      res:
2017-04-12T09:53:27.205366+00:00 app[bot.1]:       IncomingMessage {
2017-04-12T09:53:27.205367+00:00 app[bot.1]:         _readableState: [Object],
2017-04-12T09:53:27.205367+00:00 app[bot.1]:         readable: false,
2017-04-12T09:53:27.205368+00:00 app[bot.1]:         domain: null,
2017-04-12T09:53:27.205368+00:00 app[bot.1]:         _events: [Object],
2017-04-12T09:53:27.205369+00:00 app[bot.1]:         _eventsCount: 4,
2017-04-12T09:53:27.205369+00:00 app[bot.1]:         _maxListeners: undefined,
2017-04-12T09:53:27.205370+00:00 app[bot.1]:         socket: [Object],
2017-04-12T09:53:27.205370+00:00 app[bot.1]:         connection: [Object],
2017-04-12T09:53:27.205371+00:00 app[bot.1]:         httpVersionMajor: 1,
2017-04-12T09:53:27.205371+00:00 app[bot.1]:         httpVersionMinor: 1,
2017-04-12T09:53:27.205372+00:00 app[bot.1]:         httpVersion: '1.1',
2017-04-12T09:53:27.205372+00:00 app[bot.1]:         complete: true,
2017-04-12T09:53:27.205373+00:00 app[bot.1]:         headers: [Object],
2017-04-12T09:53:27.205373+00:00 app[bot.1]:         rawHeaders: [Object],
2017-04-12T09:53:27.205374+00:00 app[bot.1]:         trailers: {},
2017-04-12T09:53:27.205374+00:00 app[bot.1]:         rawTrailers: [],
2017-04-12T09:53:27.205375+00:00 app[bot.1]:         upgrade: false,
2017-04-12T09:53:27.205376+00:00 app[bot.1]:         url: '',
2017-04-12T09:53:27.205376+00:00 app[bot.1]:         method: null,
2017-04-12T09:53:27.205377+00:00 app[bot.1]:         statusCode: 400,
2017-04-12T09:53:27.205377+00:00 app[bot.1]:         statusMessage: 'BAD REQUEST',
2017-04-12T09:53:27.205378+00:00 app[bot.1]:         client: [Object],
2017-04-12T09:53:27.205379+00:00 app[bot.1]:         _consuming: true,
2017-04-12T09:53:27.205379+00:00 app[bot.1]:         _dumped: false,
2017-04-12T09:53:27.205380+00:00 app[bot.1]:         req: [Object],
2017-04-12T09:53:27.205381+00:00 app[bot.1]:         text: '{"content": ["Must be 2000 or fewer characters long."]}',

Vorschlag: Examples aus den Rules rausfiltern und separat anbieten (z.B. mit !example 510.1c)

When querying judgebot using !card we frequently get an undesired result - near as I can figure it seems to be indexing all possible matches for the search term and then returning the first match in the index, even if there's a more exacting comparison.

For example, !card fling (or !card Fling) returns Akki Boneflinger, rather than Fling. If I was making a deliberate imprecise search, I'd expect to be including wildcards - the implicit wildcard search makes it impossible to get simple-worded cards from the bot.

We use judgebot on our Discord server, and hangman always gives us

Error
You can only start one hangman game every 3 minutes.

It has worked before, but seems broken now

When Gatherer is down, using !card will cause an UnhandledPromiseRejectionWarning in Discord.js that locks the bot from taking further commands. Needs to be investigated.

Should probably be limited to Vintage, Legacy, Modern and Standard. (instead of every block-format)

!event Location city land
event wherever

!event location 20km
Events around the location

!event location date
events around the date and location

!event type
what type of event. FNM. Game Day. GP.

Hi, it will be great to show only full card and if possible in langage of our choice.

this is a message (with an inline !command pattern!) adds the closing paranthesis to the command

Discord support "reactions" to messages and the idea here would be to allow changing the displayed result for a card query to the next / previous one when somebody reacts with a ➡️ or ⬅️ emoji (or similar) to a card result message. The idea would be that the bot reacts itself to its own message with ◀️ and ▶️ and people can simply click on them (to add a reaction) and have the bot edit the message then.
It's probably pretty tricky to implement, but would make an awesome feature. 😁

Decklists form netstats or tappedout or i dont know where...

maybe with linked cards to magiccardsinfo.

It might make sense to first move away from the online API for card querying and set up a local database, based on MTGJSON.

Implement !mtr [section] based on the mtr from http://www.bluewizard.net/judgeDocs.html

Would be pretty nice to have the bot listening for people who type things like [[Hive Stone]], and respond with the proper card, and allow it to be configurable per server (toggle it on or off)

title says it all? ^^

can be rules, announcements, whatever is going on..

For example, if I write dsjghfdkjasd !help, I receive a help DM from judgebot.

On some mobile clients, putting an Emoji command into a message will only render that emoji on the desktop version of Discord. Example: :small_blue_diamond:

bug

Encapsulating links, files, etc into <> brackets seems to remove the preview in discord. The giant rules resources logo is not needed in every link to rules material.

New API: https://whatsinstandard.com/api/v5/sets.json

Hi @bra1n
Thanks for your great work with judgebot. :)

I really would like to be able to click on the thumbnail like when using !hangman and failing, it would be nice to have the ability to zoom into the card image/art. (https://github.com/bra1n/judgebot/blob/develop/modules/card.js#L241)

What do you think, shouldn't be that hard to implement?

Cheers

Sam

Idea: use a regular expression to see if someone queries for a rule (123.4a) or a definition (lifelink)

Create a parser that converts the magic judge rules resources to readable text for discord.

The bot shouldn't make requests for resources it has recently accessed, in order to speed up the query. In theory, the whole MTR and IPG could be served from cache.

• IPG
• MTR
• Card

Or any other sections but "definition".

Until Scryfall adds it to their API: https://github.com/scryfall/feedback/issues/284

If !card produces a result which is longer than discord's character limit of 2000, the command fails.

An example would be !card ice.

Hello here. Maybe We can imagine to use printed_text instead of oracle_test in function generateDescriptionText. I'm using this bot mainly with lang:french and the displayed text is the english text.
Could we fix that ? @bra1n

...instead of putting the URL to the image into the message.
This way, the message itself will be cleaner (no Gatherer image URL anymore!), plus the content is clearly separated and maybe can be filtered in Discord.

For example: !help define

As mentioned in #32, I think the version of the IPG available under https://sites.google.com/site/mtgfamiliar/rules/ is easier to parse, it also provides the whole IPG on a single page, which makes it simpler to read it in once on startup, so the bot doesn't have to make a separate request on each !ipg command.

!ipg hce -> !ipg 2.3
!ipg mt -> !ipg 2.1
etc.

!banlist format
would show the banned card in the format chosen.

While the bot is great, a large number of rules in mtg are split into several smaller subrules

Either allowing an option to simply return all subrules of the requested rule, or allowing multiple arguments to !cr would be useful when explaining a full rule to someone, instead of the rule being returned with breaks as you request each subrule in a seperate !cr

Probably some part of the result (with/without image) magic breaks this.

Hi.
The cardimage currently doesn't show up after completing a game of hangman. The issue seems to be that scryfall have changed their api.

Changing card.image_uri on row 78 in hangman.js to one of the following should fix it as far as I can tell:

card.image_uris.small
card.image_uris.normal
card.image_uris.large
card.image_uris.png

some cards also seems to have
card.image_uris.art_crop
and
card.image_uris.bordercrop
but not all of them.