Dream Maker was not compiling the new atom.override var properly in some cases, which could cause the server to become confused when using other variables in unusual cases.
BYOND Version:482
Operating System:Windows 7 Ultimate 64-bit
Web Browser:Chrome 12.0.742.68
Applies to:Dream Maker
Status: Resolved (484)

This issue has been resolved.
Descriptive Problem Summary:
If one creates an environment and then creates a variable with the exact same name (minus the .dme extenstion) the variable will default to 0 regardless of its initialization.

Numbered Steps to Reproduce Problem:
1) Create a new environment (ie: cake)
2) Create a new .dm file
3) In that dm file, define a variable with the same name as the environment (ie: mob/var/cake)
4) Output the variable (ie: world << cake)

Code Snippet (if applicable) to Reproduce Problem:
cake = "I AM CAKE!"

world << cake

Expected Results:
The name of the environment has no relation to the value of a variable

Actual Results:
A variable with the same name as the environment defaults to 0

Does the problem occur:
Every time? Or how often?
Every time
In other games?
In other user accounts?
On other computers?

When does the problem NOT occur?
If the variable or environment are renamed

Did the problem NOT occur in any earlier versions? If so, what was the last version that worked?

Rename the variable or environment
Huh, the environment thing turned out to be a red herring after all.