This page is the gateway to various game aids for use with
Degenerates® family of games (hereafter referred to
as "DD"). These utilities include editors for creating custom cards
with the same overall style as those which come with the
Degenerates is a registered trademark
of Goblinko. Goblinko is
not associated with this site, its software, or its content, other than having provided
explicit permission to reproduce certain copyrighted materials here. This site is created and
maintained by fans, for fans, because
fans are cool (haha!).
Easily create your own custom cards of various types...
Encounter cards (and similarly-structured spinoffs):
the infrastructure is more or less complete but implementing editor apps for
these is far more complicated (and may never happen, meaning they'll only be usable by people
willing to hand-write their own JSON). See the Hirelings variant
for some examples of Encounter-like cards and the scratchpad page for
various doodlings in that direction.
Documentation: the tools linked to here are all
based on a framework documented
in this document.
This software was initially implemented for use in/by the
Android application, to replace its use of scanned copies of game cards. In the meantime
it has (also) become a standalone set of tools unrelated to that application (with no real
functional overlap other than the display of cards (for different purposes)).
Source code: this software is Open Source, free for
any use, though the icons it uses are only free for non-commericial use (see the complete
license in the docs above). The sources can be found at:
Can be downloaded and run locally:
see the instructions at the source repository link (the previous entry in this list).
Eye-melting Colors!Not my idea. That's just how the game rolls.
These sample cards are rendered on-the-fly by this toolit.
(Tap/click a Skill card to toggle its Skill and Mastery views.)
Note that these are not images, but are rendered using only HTML
and a collection of the game's SVG-format icons which the
publisher made available for use by fans.
Printing Your Degenerate Cards
Note that the on-screen colors used by these apps were chosen not
because they look great on the screen, but because the print out
(on my printer) quite close to the originals.
The instructions for printing your newly-created cards is the
same for all of the apps linked to above. In short, they rely on
modern browsers' ability to print web pages to PDF files. The
card editors render the cards at either their "real" size
(41x63mm) or twice that size (to make them more readable while
editing). When printing, the user will need to be aware of which
card size is currently being displayed (the visual difference is
drastic, so there's really no mistaking the two).
Note that the generated cards are created from HTML and, except
for the icons, are not images. That means that you will
not find a "download image" option in your browser's context
To print them, use your browser's Print to PDF feature, keeping in mind that:
For printing purposes, these apps disable (via CSS) all UI
elements except for the cards, so those won't be part of the
printout. The printouts should include only the
Printing at 600dpi or higher provides the best results. At 150-300dpi
the text is certainly readable but will not be quite as sharp.
When printing cards rendered in mini mode, print at 100% scale.
When printing maxi-sized cards, configure the printout for 50% scale.
Those will, when the PDF is printed out to paper, result in cards sized to
within a fraction of a millimeter of the game's official cards.
The CSS used by the apps tells the browser that it "should" print the
background colors for the cards. If the resulting PDF has cards with no
background colors, then either the "print background colors" option
needs to be enabled in the browser's printer configuration (if the
option is available) or the browser may not support that feature (in
which case try Firefox or Chrome).
Testing is performed using only Firefox and Chrome. In my
tests, Firefox has consistenly provided the best printing
results, especially for apps which print many cards: in such a
configuration, Firefox will (under the right circumstances)
wrap the cards so that they are spread across pages, whereas
Chrome will truncate cards across page boundaries
(or may do so, depending on its mood). Results with
other browsers is unknown, but any browser based on other of
those (which is no small number of browsers) should work just
For best results, slip printed-out cards into sleeves for added stability.
Alternately (or in addition), print them out on cardstock (if possible)
or sticker paper, and/or glue them to heaver stock after printing.
Next-level Stuff: Converting Cards to SVG!
It's possible to get your cards in SVG format! Both Firefox and
Chrome, when printing these cards, "vectorize" them, rather than
convert them to images. This means that the PDF can be processed
by a tool like pdf2svg or dropped into Inkscape to
extract the card in SVG format. When doing so in Inkscape
(simply drop the PDF into an opened Inkscape window), make
sure to select its "Poppler" import option (which is
not the default), or the cards' font will be completely
massacred. The Poppler option will convert all text into
"paths". The result is a much larger file, but it retains 100%
fidelity (or extremely close to it) with the original rendering
from the web page, and can be scaled up or down to any size with
no loss of quality.
For those with any scripting experience, the process of exporting
"printed" PDFs to SVG or PNG can be automated, as demonstrated
shell script (to see the latest version of that file, click
the "file:[...]" link of the top-most entry on that page).
Licenses and Permissions
This site uses materials licensed, or permitted for use, from
the following sources:
The card iconography and the full text of certain, Skill, Weakness, and Triumph cards
is copyright Goblinko, used with permission.
(In selection lists such cards are, in browsers which support it, styled
like this. Not all browsers support styling selection list entries, however.)
These tools use only a single cookie for that one user
who logs in to the administrative page. i.e. only me. Certain
parts may, at some point, be extended to use so-called "local
storage" to allow the apps to communicate local changes with
each other without having to save them to the server, but any
such data would be stored only on your computer and never sent
to the server.