ID:1483467
 
BYOND Version:500
Operating System:Windows Vista Home Basic
Web Browser:Chrome 32.0.1700.76
Applies to:Dream Seeker
Status: Open

Issue hasn't been assigned a status value.
Descriptive Problem Summary:
If control_freak is enabled, attempting to call up the profiler in Dream Seeker using .profile or the Server menu will fail to show anything.

Numbered Steps to Reproduce Problem:
1) Make an environment.
2) Set control_freak to anything (mine is set to CONTROL_FREAK_ALL|CONTROL_FREAK_MACROS)
3) Compile & Run Dreamseeker
4) Try to open the profiler

Code Snippet (if applicable) to Reproduce Problem:


Expected Results:
Profiler should be accessible regardless of control_freak's setting.

Actual Results:
Profiler fails to show up.

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

When does the problem NOT occur?
When control_freak is disabled.

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.)

Workarounds:

Have you tried ".debug profile"?
That also does not work. You can't enter it into the input at all, even with quotes, and a macro with that command doesn't do anything for me while control_freak is on.
In response to Devourer Of Souls
Devourer Of Souls wrote:
a macro with that command doesn't do anything for me while control_freak is on.

That seems like an oversight to me - the profiler should always be accessible to developers!
As a work-around for now, I'd suggest try using the browser-based profiler. You'll need a browser conttol. It'll open in thr default.
and then, the simple command byond://?debug=profile needs to be ran. This is a built-in client/Topic() call, so be sure to call the parent.
Well, in a way, this is expected behaviour, isn't it?

Much of the point of control_freak is that you've restricted macros in general, so this profile function is not available to the host for instance, with control_freak on.

Similar to enabling debugging by checking #ifdef DEBUG for adding extra logging, presumably you'd turn off control_freak for a debug build with the same.