ID:2351767
 
Not a bug
BYOND Version:511
Operating System:Windows 10 Enterprise 64-bit
Web Browser:Firefox 58.0
Applies to:Dream Daemon
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:
world.log seems to persist between runs of different .dmbs. This caused me some confusion.
Numbered Steps to Reproduce Problem:
- Compile the included projects
- Open Dream Daemon
- Select test1.dmb, run it. No message will be printed to the DD output, as expected.
- Stop the server.
- Select test2.dmb, run it. No message will be printed to the DD output, despite test2.dm not modifying world.log. The output is instead written to the log file specified by test1.dm.
Code Snippet (if applicable) to Reproduce Problem:
https://github.com/DamianX/junk/raw/master/whatever.zip

Expected Results:
Expected world.log to be null(?) at server start
Actual Results:
world.log retains the value set by the previous run
Does the problem occur:
Every time? Or how often? Every time.
In other games? N/A
In other user accounts? N/A
On other computers? N/A

When does the problem NOT occur?
Always happens.
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.) Don't know, but it works like this on 510.1347 and 512.1405, so I assume it was always like this.
Lummox JR resolved issue (Not a bug)
This is actually intended behavior. Generally it's desirable to get the collected output from several runs, especially if the world uses Reboot() to reset rounds.