By using this extension, you understand that your server could get banned off Disboard. Use this at your own risk.
Not against Discord's ToS!
This Browser Extension simply auto-bumps your Discord server on Disboard. Useful for easily gaining more members in your server!
Until I decide to pay the dev licence fee, this will be the way to install the extension.
- Download (or clone) the repository and (if you downloaded) extract the folder into a directory.
- Visit
chrome://extensions/
(copy this into the search bar) and enable Developer mode.
- Drag and drop the folder into
chrome://extensions/
.
That's it!
- Download (or clone) the repository and (if you downloaded) extract the folder into a directory.
-
Visit
about:debugging#/runtime/this-firefox
(copy this into the search bar). -
Click on 'Load Temporary Add-on...' and locate the
manifest.json
file in the folder you extracted.
That's it! (You may have to reinstall the add-on on restarts)
-
Click on the
๐ ฑ๏ธ icon to pick which server to bump in that tab. -
Keep it open or it will not work. TIP: Pin the tab! (Right Click > "Pin Tab")
-
[Multibumping!] Optionally have multiple tabs opened for different servers!
Q: Why does the extension randomly freeze or not bump?
A: A work around to this issue (mentioned in #4) is to install this auto refreshing extension and run it along side.
Q: Why doesn't the timer correspond with the time left to bump?
A: This is to avoid being de-listed of Disboard and is normal. It can be disabled by switching off Safety Mode in the extension popup.
Q: Why do I get a message telling me that this is unsafe?
A: The warning "Disable developer mode extensions" is displayed in Chrome when you install non Chrome Web Store extensions in the browser. Read more and learn how to disable it here. If you would like to continue using the extension then simply press 'X' when you see this message.
Q: Why do I get an error saying "Unrecognized manifest key 'browser_specific_settings'."
A: In Chrome, if you look into the errors of the extension, you may find this error. It is completely normal and the extension will still continue to function properly. The reason for this error is that browser_specific_settings
is used for Firefox add-on support but Chrome doesn't recognize this.
Q: IT STILL DOESN'T WORK!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!???
A: Feel free to open an issue if the existing ones don't solve your problem. Also you can chat with us here!