PPT Episode #45: The Before “The Return of Dr. Sloth” Plot Edition PPT Episode #47: The Return of Dr. Sloth Walkthrough Edition
Feb 08

host_kym PPT Episode #46: The Dr. Sloth Plot Decoder Program Outrage Edition host_laura.gif

With the announcement yesterday by Neopets that the use of the decoder programs to help complete The Return of Dr. Sloth plot was illegal, thousands upon thousands of Neopians took up arms to defend their right to use these programs. What are their arguments? Do they have merit? What do the hosts think? Tune into this impromptu recording to find out.

 
icon for podpress  Standard Podcast [36:05m]: Play Now | Play in Popup | Download (2245)

Popularity: 14% [?]

RSS feed | Trackback URI

4 Comments »

2008-02-08 01:08:16

[...] right to use these programs. What are their arguments? Do they have merit? What do the hosts think? Tune into this impromptu recording to find out. Share and Enjoy: These icons link to social bookmarking sites where readers can share and [...]

(Comments wont nest below this level)
 
2008-02-08 01:55:00

[...] a new mixing program that allows live recording, Lee and myself got together on a whim and recorded episode 46 of The PPT Show: The Dr. Sloth Plot Decoder Program Outrage [...]

(Comments wont nest below this level)
 
Comment by quincy
2008-02-15 22:01:38

yeah, I’m one of those people who can’t go on in the plot………..after being good at the first plot after I joined (Cyodrakes Gaze) the others seemed harder and I felt left out of some because I didn’t know what to do. I guess this one won’t be any different………..

(Comments wont nest below this level)
Comment by Lee
2008-02-18 15:09:25

Keep working on it! Head over to the PPT Forums for some great advice on the plot.

 
 
Name (required)
E-mail (required - never shown publicly)
URI
Subscribe to comments via email
Your Comment (smaller size | larger size)
You may use <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong> in your comment.