ID:1986042
 
Not a bug
BYOND Version:508
Operating System:Windows 10 Pro 64-bit
Web Browser:Chrome 46.0.2490.86
Applies to:Dream Maker
Status: Not a bug

This is not a bug. It may be an incorrect use of syntax or a limitation in the software. For further discussion on the matter, please consult the BYOND forums.
Descriptive Problem Summary:
I'm attempting to use some fancy text art, but I'm getting hit with the following error when I try this:

undefined text macro or escape sequence: \__/

It looks like macros and escapes are being read from the special text document syntax.

Bug? Or working as intended?

Numbered Steps to Reproduce Problem:
1. Copy and paste my code into Dream Maker
2. Compile
3. Observe the generated error

Code Snippet (if applicable) to Reproduce Problem:
mob
Login()
src << splashscreen

var/splashscreen={"
_______ __ __ ______ __
/_ __(_) /_/ /__ /_ __/__ _____/ /_
/ / / / __/ / _ \ / / / _ \/ ___/ __/
/ / / / /_/ / __/ / / / __(__ ) /_
/_/ /_/\__/_/\___/ /_/ \___/____/\__/
"}


client
Command(cmd as command_text)


Expected Results:
For the text art to compile as text.

Actual Results:
Dream Maker detects macros and escapes due to the format (positions of special characters) of the text art.

Does the problem occur:
Every time? Or how often? Every time
In other games? Attempted several variations of the given code
In other user accounts? Unknown
On other computers? Unknown

When does the problem NOT occur?
Unknown

Did the problem NOT occur in any earlier versions? If so, what was the last version that worked? (Visit http://www.byond.com/download/build to download old versions for testing.)
Unknown

Workarounds:
Unknown
I have no idea if this is intended behavior, but it is the behavior I would expect (despite the vagueness of the reference). The only difference this entry mentions is being able to use un-escaped double quotes and linebreaks- ignoring escape sequences could potentially be kind of annoying.
In response to Audeuro
I see. I don't understand the value of escapes in the special text document syntax, but maybe I'm just approaching this in an improper way to begin with. Got any workaround ideas?
either don't use backslashes, or double them up after making the art look how you want
In response to GinjaNinja32
The second option sounds good enough for me. Thanks.
Escapes are processed in extended string blocks, so this is intended.
Lummox JR resolved issue (Not a bug)