Follow TV Tropes

Following

Discussion History VideoGame / Undertale

Go To

[010] DonaldthePotholer Current Version

26th May '16 at 07:48:56 PM

Changed line(s) 1 from:

n

Was tempted to add this line to the

to:

Was tempted to add this line to the \"Operation Briefcase\" example of MoodWhiplash. Hogan utters it in that episode after the courier codenamed \"Hercules\" was declared dead by the (unnamed) medical sergeant:
--->\'\'\'Hogan\'\'\': This plan [had] better work; it\'s already got an expensive price tag.

[009] DonaldthePotholer

26th May '16 at 07:48:33 PM

Changed line(s) 1 from:

n

Was tempted to add this line to the

to:

Was tempted to add this line to the \"Operation Briefcase\" example of MoodWhiplash. Hogan utters it in that episode after the courier codenamed \"Hercules\" was declared dead by the (unnamed) medical sergeant:
--->\'\'\'Hogan\'\'\': This plan [had] better work, it\'s already got an expensive price tag.

[008] dan96kid1

24th Nov '15 at 01:58:27 PM

Changed line(s) 1 from:

n

After some testing, Folder A-F opens in Firefox but not chrome. I thought a commented-out trope in the folder was what \

to:

After some testing, Folder A-F opens in Firefox but not chrome. I thought a commented-out trope in the folder was what \\\"broke\\\" it for chrome. After giving the trope context and un-commenting it out, Folder A-F STILL won\\\'t open in chrome. When I used Chrome\\\'s dev tools to inspect the folder, the console reported:

Uncaught [=TypeError=]: Cannot read property \\\'display\\\' of main.js?rev=100:557\\\\\\\\
undefined

[007] dan96kid1

24th Nov '15 at 01:57:56 PM

Changed line(s) 1 from:

n

After some testing, Folder A-F opens in Firefox but not chrome. I thought a commented-out trope in the folder was what \

to:

After some testing, Folder A-F opens in Firefox but not chrome. I thought a commented-out trope in the folder was what \\\"broke\\\" it for chrome. After giving the trope context and un-commenting it out, Folder A-F STILL won\\\'t open in chrome. When I used Chrome\\\'s dev tools to inspect the folder, the console reported:

Uncaught [=TypeError=]: Cannot read property \\\'display\\\' of main.js?rev=100:557//
undefined

[006] dan96kid1

24th Nov '15 at 01:57:03 PM

Changed line(s) 1 from:

n

After some testing, Folder A-F opens in Firefox but not chrome. I thought a commented-out trope in the folder was what \

to:

After some testing, Folder A-F opens in Firefox but not chrome. I thought a commented-out trope in the folder was what \\\"broke\\\" it for chrome. After giving the trope context and un-commenting it out, Folder A-F STILL won\\\'t open in chrome. When I used Chrome\\\'s dev tools to inspect the folder, the console reported:

Uncaught [=TypeError=]: Cannot read property \\\'display\\\' of main.js?rev=100:557
undefined

[005] dan96kid1

24th Nov '15 at 01:56:52 PM

Changed line(s) 1 from:

n

After some testing, Folder A-F opens in Firefox but not chrome. I thought a commented-out trope in the folder was what \

to:

After some testing, Folder A-F opens in Firefox but not chrome. I thought a commented-out trope in the folder was what \\\"broke\\\" it for chrome. After giving the trope context and un-commenting it out, Folder A-F STILL won\\\'t open in chrome. When I used Chrome\\\'s dev tools to inspect the folder, the console reported:

Uncaught [=TypeError=]: Cannot read property \\\'display\\\' of main.js?rev=100:557

undefined

[004] dan96kid1

24th Nov '15 at 01:56:38 PM

Changed line(s) 1 from:

n

After some testing, Folder A-F opens in Firefox but not chrome. I thought a commented-out trope in the folder was what \

to:

After some testing, Folder A-F opens in Firefox but not chrome. I thought a commented-out trope in the folder was what \\\"broke\\\" it for chrome. After giving the trope context and un-commenting it out, Folder A-F STILL won\\\'t open in chrome. When I used Chrome\\\'s dev tools to inspect the folder, the console reported:

Uncaught [=TypeError=]: Cannot read property \\\'display\\\' of main.js?rev=100:557
undefined

[003] dan96kid1

24th Nov '15 at 01:56:13 PM

Changed line(s) 1 from:

n

After some testing, Folder A-F opens in Firefox but not chrome. I thought a commented-out trope in the folder was what \

to:

After some testing, Folder A-F opens in Firefox but not chrome. I thought a commented-out trope in the folder was what \\\"broke\\\" it for chrome. After giving the trope context and un-commenting it out, Folder A-F STILL won\\\'t open in chrome. When I used Chrome\\\'s dev tools to inspect the folder, the console reported:

Uncaught [=TypeError=]: Cannot read property \\\'display\\\' of main.js?rev=100:557 undefined

[002] dan96kid1

24th Nov '15 at 01:55:55 PM

Changed line(s) 1 from:

n

After some testing, Folder A-F opens in Firefox but not chrome. I thought a commented-out trope in the folder was what \

to:

After some testing, Folder A-F opens in Firefox but not chrome. I thought a commented-out trope in the folder was what \\\"broke\\\" it for chrome. After giving the trope context and un-commenting it out, Folder A-F STILL won\\\'t open in chrome. When I used Chrome\\\'s dev tools to inspect the folder, the console reported:
Uncaught [=TypeError=]: Cannot read property \\\'display\\\' of main.js?rev=100:557 undefined

[001] dan96kid1

24th Nov '15 at 01:55:37 PM

Changed line(s) 1 from:

n

After some testing, Folder A-F opens in Firefox but not chrome. I thought a commented-out trope in the folder was what \

to:

After some testing, Folder A-F opens in Firefox but not chrome. I thought a commented-out trope in the folder was what \\\"broke\\\" it for chrome. After giving the trope context and un-commenting it out, Folder A-F STILL won\\\'t open in chrome. When I used Chrome\\\'s dev tools to inspect the folder, the console reported:
Uncaught [TypeError]: Cannot read property \\\'display\\\' of main.js?rev=100:557 undefined

Top