You really do attack the problem. But since I didn't explicitly see it, and am a bad reader, I just want to be sure that implementing...

use Cpanel::JSON::XS::Type;

sub makeJSON {
    (my $hashref) = @_;

    my $json = encode_json($hashref, {returnvalue => JSON_TYPE_INT,
                                   username    => JSON_TYPE_STRING,
                                   userid      => JSON_TYPE_STRING,
                                   status      => JSON_TYPE_STRING,
                                   filename    => JSON_TYPE_STRING,
                                   rawfilename => JSON_TYPE_STRING,
                                   ticket      => JSON_TYPE_STRING,
                                   message     => JSON_TYPE_STRING});
    return $json;
}
[download]

...covers my bases.

Although am still a little offset that sometimes it turned it into a string, and sometimes not. But I'll get over it.

Again, thanks for making slides to let people know.

You also need to

use Cpanel::JSON::XS;
[download]

Its encode_json takes the extra parameter, the ::Type module just exports the types' names.

BTW,

(my $hashref) = @_;
[download]

is usually written

my ($hashref) = @_;
[download]

so you can easily add more parameters if needed without having to move the parenthesis around.
map{substr$_->[0],$_->[1]||0,1}[\*||{},3],[[]],[ref qr-1,-,-1],[{}],[sub{}^*ARGV,3]

Yes,

use Cpanel::JSON::XS;

was already in there. Just bad cut & pasting. As for:

(my $hashref) = @_;

was a typo that seems to work, although I will fix that now. Just to ask tho, is there a reason I shouldn't syntax for single variables?