Write ASCII-Art Obfuscated Code, read as, and resulting in: "DFTBA" The challenge is to write the most elaborate code, embedded in ASCII art that reads and prints "DFTBA".  For example, the following reads DFTBA:

oooooooooo.   oooooooooooo ooooooooooooo oooooooooo.        .o.       
`888'   `Y8b  `888'     `8 8'   888   `8 `888'   `Y8b      .888.      
 888      888  888              888       888     888     .8"888.     
 888      888  888oooo8         888       888oooo888'    .8' `888.    
 888      888  888    "         888       888    `88b   .88ooo8888.   
 888     d88'  888              888       888    .88P  .8'     `888.  
o888bood8P'   o888o            o888o     o888bood8P'  o88o     o8888o 


And the following, in bash prints DFTBA

echo "DFTBA"


The challenge is to write one that does both. 

Winning conditions

Valid answers, (all conditions at my discretion) 


Can be clearly read as DFTBA
Print DFTBA when executed
Must be functional with no Internet connection
have letters of equal height
must not have more than 80 columns
must not have more than 10 rows


Points (highest sum wins)


Rows * Columns / 32
Readability: 25 for legible, 50 for very clear
1 point for each different non-whitespace character used


Restrictions

These may be used for something, so all responses are assumed to be released into the public domain.  If you can't, or choose not to release your answer into the public domain: post a comment/response to the original question saying "The answer authored and/or shared by me, may not be considered to be in the public domain".

Non-public domain answers are welcome too!  Just make sure to specify :-)

What is DFTBA?

It sometimes stands for "Don't Forget To Be Awesome", but not always... Long story...  This related song might help explain (or confuse).
Piet, Score Uncertain (153ish)



I understand that this doesn't strictly fit within the specifications (requiring ASCII art), however the source code does provide a very readable DFTBA. The trace is below.

Piet ignores every colour that doesn't mean anything. As a result, I used gray as the generic "comment colour" to outline and the like. The gray doesn't get interpreted (as you'll see in the trace). I wanted to make it clear which pixels were in the program and which were not.

I've used 15 colours, which is 13 without whitespce. It is 89x32 pixels, though could be compressed more. I used 4 op-codes (subtract, divide, push and outputc). Maybe if using scoring how I would think, 153?

Probably doesn't warrant a score, but was an interesting exercise. Having never used Piet before, I've never done so much trial-and-error programming! I needed npiet extensively, and its trace. I still can't figure out how the movement of the cursor works with any stability!

How it works:


D, F, T are constants for their respective ASCII letters that are then pushed to the stack, and the OUTC command called
B is the ASCII for B x 2 (needed to be to look good), which is pushed to the stack, then divided by two, then duplicated on the stack and the OUTC command called
Note the earlier duplication. That was because I couldn't make A look good in so few characters. I push 1 to the stack, subtract (making the ASCII code for A) and then the whole A character is the opcode for OUTC - doesn't matter the size, because it's an operation not a constant