Here are some common questions about cord.nvim that nobody asked, yet we answered anyway. If you don't find your answer here or in the[Troubleshooting Guide](./Troubleshooting.md), don't hesitate to ask in our[Discord community](https://discord.gg/q9rC4bjCHv) or[GitHub Discussions](https://github.com/vyfor/cord.nvim/discussions)!

Some common questions about cord.nvim that nobody asked, yet we answered anyway. If you don't find your answer here or in the[Troubleshooting Guide](./Troubleshooting.md), don't hesitate to ask in our[Discord community](https://discord.gg/q9rC4bjCHv) or[GitHub Discussions](https://github.com/vyfor/cord.nvim/discussions)!

Cord istested with Neovim**0.6.0** orlater. Although, we encourage you to use the latest stable version of Neovim, as it provides the best experience and performance. However, if you're running an older version, and find that Cord is not working as expected, please open an issue and we'll try to help you out.

Cord iscompatible with Neovim**0.6.0** ornewer.

Nope, you don't need Rust anymore! Cord will automatically download the necessary server binary from GitHub. If you want to build the binary from source, refer to[this](./Build.md) page.

No, you don't need Rust anymore.

Cord will download the server binary for you.

If you'd rather build it yourself, check the[Build guide](./Build.md).

There are two ways to see logs:

You can check the logs in two ways:

1.Pass in the desiredlog levelto the`log_level` fieldin yourconfiguration. Logs at that level andabove willbe output to`:messages`.

1.Set alog level in yourconfig. Messages at that level(andhigher) willshow up in`:messages`.

require'cord'.setup {

}

2. Set the`CORD_LOG_FILE` environment variable to a file path. Thiswill redirect alllogs tothat file. This is useful for debugging as trace and debug logs can be very verbose and overwhelming in the editor.

2. Set the`CORD_LOG_FILE` environment variable to a file path. Thissaveslogs toa file instead of spamming your editor, which is especially useful when using`trace` or`debug` levels.

Yes, you will have to create an application with the desired name in the[Discord Developer Portal](https://discord.com/developers/applications).

Then, copythe application ID and put it in the`editor.client` field in your`cord.nvim` configuration.

To do this, you will have to create an application with the desired name in the[Discord Developer Portal](https://discord.com/developers/applications).

Then, copyits application ID and put it in the`editor.client` field:

Example:

require'cord'.setup {

editor= {

Cord's server keeps running intentionally. In fact, this is one of the key design features that sets it apart from similar plugins. It remains active in the background to maintain a continuous connection to Discord, which helps avoid hitting Discord's rate limits on reconnections, especially useful if you often restart Neovim rather than maintaining a single long session. If you prefer not to have it running, you can adjust the`advanced.server.timeout` setting.

That's intentional.

Cord's server keeps running to maintain a single continuous connection to Discord and avoid hitting rate limits from reconnecting too often.

This is especially useful if you restart Neovim a lot.

If you'd rather shut it down sooner, there's the`advanced.server.timeout` option.

See[Special Environments](./Special-Environments.md#-custom-discord-clients).

Cord detects different buffers based on their filetype, and occasionally their filename. See the list of supported filetypes[here](https://github.com/vyfor/cord.nvim/blob/master/lua/cord/plugin/activity/mappings.lua). If it's not listed, it usually means one of two things:

- It has not been added yet — feel free to[open an issue](https://github.com/vyfor/cord.nvim/issues/new/choose) and we'll add it.

- It cannot be detected:

-*Languages* that cannot be detected by filetype or filename alone, have to be configured to be detectable, as explained in[here](https://github.com/vyfor/cord.nvim/wiki/Assets#-tip).

-*Plugins* are required to override current buffer's`filetype`, or otherwise Cord will not be able to detect it.

Cord detects buffers mostly by filetype (and sometimes by filename).

Check the list of supported filetypes[here](https://github.com/vyfor/cord.nvim/blob/master/lua/cord/plugin/activity/mappings.lua).

If the language or plugin you use isn't found on the list, please[open an issue](https://github.com/vyfor/cord.nvim/issues/new/choose).

Just keep in mind:

-**Languages** that don't expose a clear filetype or filename need extra setup (see[this page](https://github.com/vyfor/cord.nvim/wiki/Assets#-tip)).

-**Plugins** need to override the buffer's`filetype`, otherwise Cord won't be able to recognize them.

Rich Presence updates now take longer to appear because Discord enforces a rate limit on how frequently these updates can be sent. Originally, Discord's documentation allowed one update every 15 seconds—a limit that mostly affected mobile and web clients while desktop users saw instantaneous changes. However, after a recent overhaul of Discord's rich presence interface, this, or a similar rate limit appears to be strictly applied across all platforms, causing the delays you're noticing. From my point of view, this rate limit is ridiculously high, and should be drastically reduced. Perhaps a collaborative effort from the community could make them reconsider their decision, but there's nothing I can do on my end, I'm afraid. See the relevant[discussion](https://github.com/vyfor/cord.nvim/discussions/196).

After the recent update, Discord started to*properly* rate-limit how often your Rich Presence can update. The exact numbers aren't known yet.

Not caused by Cord.

See the[discussion](https://github.com/vyfor/cord.nvim/discussions/196) for details.

It used to work as expected, but I suspect that Discord introduced a bug in recent updates. When you omit timestamps in your activity payload, the absence of a timer is expected at first. However, within seconds the timer reappears and resets to zero on every new activity update. In my testing, this reappearance has been inconsistent—sometimes happening immediately, and other times after a couple of seconds. Interestingly, during the brief period without the timer, updates go through instantly without any apparent rate limiting on the client side. This behavior appears to be due to changes in how Discord handles rich presence updates internally, rather than an issue with the plugin itself. See the relevant[discussion](https://github.com/vyfor/cord.nvim/discussions/196#discussioncomment-12221577).

Disabling timestamps was previously possible but Discord appears to have introduced a bug.

If you omit the timestamp now, it starts to misbehave, with the timer initially briefly disappearing but then reappearing and resetting to zero whenever the activity updates. No can do on our end.

Not caused by Cord.

See the[discussion](https://github.com/vyfor/cord.nvim/discussions/196#discussioncomment-12221577) for details.