Deviant Login Shop  Join deviantART for FREE Take the Tour
Group Info Group Founded 4 Years ago Statistics 352 Members
52,628 Pageviews565 Watchers



:icon24bps: 24bps Serving the devious


You're not here because you're not logged in
  • :iconlord-hayati:
    Visited here 5 hours, 24 minutes ago
    Isn't a member
  • :iconneolytek:
    Visited here 10 hours, 10 minutes ago
    Isn't a member
  • :iconiamoret:
    Visited here 15 hours, 43 minutes ago
    Isn't a member
  • :iconeuxiom:
    Visited here 1 day, 5 hours ago
    Isn't a member
  • :icondimensiondragonfire:
    Visited here 1 day, 10 hours ago
    Isn't a member

Bug reporting

:megaphone: Found a bug in SuperdAmn? Send the group a note, and our team will try to help you!

SuperdAmn Breaks, Panic Ensues!

The chatrooms were updated earlier this week in a way that broke not only SuperdAmn but many if not most other userscripts. If you had chat-related userscripts enabled you may have been unable to load dAmn at all. The changes involved updates related to DWait. Another update was made soon afterwards to fix bugs which the update before introduced to dAmn itself (not just to userscripts), and this helped alleviate most of the problems. Most Chrome users were able to use SuperdAmn without any issues, but Firefox users still had a half working script at best.

Whether or not you have a semi working version on Firefox, or a fully working version on Chrome, you should still update any version of the script that was obtained before this blog post was made. Additional changes have been made to the updater code.

New Updater

Many people seem to have already realized that the recently fixed SuperdAmn (version 1.0.2) was available on GitHub.

As mentioned in the last blog post, SuperdAmn has been on GitHub for several months now but it wasn't being made full use of. Taking the most advantage of the ease of collecting fixes and features from other developers that GitHub offers, future versions of SuperdAmn will now be updated directly from GitHub instead of the old host, 24bps. As mentioned previously, even if you have the previous, recently fixed version of SuperdAmn (version 1.0.2), you should still update to the latest one from the links below (version 1.0.3).


:pointr::pointr: Click here to install SuperdAmn! :pointl::pointl:
Requires Mozilla Firefox and the Greasemonkey extension.
:pointr::pointr: Install SuperdAmn for Chrome (Detailed Chrome installation instructions) :pointl::pointl:
The Safari version is currently outdated. When it's been updated a link will be available on this journal.

Small note for developers: If you're unsure of what to do to fix any of your scripts or any broken scripts by other people that you happen to use, wrap any code that initializes modifications to the client or references dAmn-related functions/variables in any other way in a call to DWait.ready(). This is an example taken straight from the latest SuperdAmn of the fix in action:

// We need to use DWait to make this work properly now
DWait.ready(['jms/pages/chat07/chatpage.js', 'jms/pages/chat07/dAmn.js', 'jms/pages/chat07/dAmnChat.js'], function() {
More Journal Entries


Add a Comment:
Hidden by Owner
To all Chrome users: the extension seems to be working once again. I turned it back on today, and its working just fine.
My Firefox user friends don't seem to be having the same luck.
StargazerSammie Apr 10, 2014  Hobbyist Digital Artist
Chrome was repaired earlier today. deviant-garde did the fix and he's apparently still working on the Firefox version
I didn't fix it for Chrome. It just works now for Chrome. The fix for Firefox should be available soon. It's ready and waiting.
Let us know when and where to get the fix for Firefox please? :)
(2 Replies)
Good to hear that the fix is in progress *waits for it* time stamps and the shortcut for editing topics makes being a chat room mod much easier
StargazerSammie Apr 10, 2014  Hobbyist Digital Artist
Oops, sorry then! I must have read it wrong or something. I apologize for the mix up and I'm looking forward to Firefox fix when it happens c:
(1 Reply)
So the latest issues is simply because the dAmn has been updated and that SuperdAmn will need to update to work with it now?
It's highly likely because I've got dAmn Autojoin running and it's doing just fine from the looks of it.
I believe so
Add a Comment: