Why the urge to solve the parsing with a single regex? I would solve it differently. I wouldn't use %attr_value to group "tags" like 'former', 'admin' and 'trainee' together with the role. I would so something like: 
my %roles      = qw /consultant  -1
                     editor       0
                     programmer   2/;
         
my %pre_attrs  = qw /former      -2/;
            
my %post_attrs = qw /trainee     -1
                     admin        1/;  
            
my $def_score  = -2;
            
my @trust      = ([full   =>  2],
                  [strong =>  1],
                  [normal =>  0],
                  [weak   => -1],
my $def_trust  =  'none';
        
my $max_score = -10000;   # Some big, negative number.
foreach my $type (@usertypes) {
    my $score = 0;
    my $attrs = 0;
         
    while (my ($key, $value) = each %pre_attrs) {
        if ($type =~ s/\Q$key\E\s*//) {
            $score += $value;
            $saw_pre = 1;
            last; 
        }
    }
         
    while (my ($key, $value) = each %roles) {
        if ($type =~ s/\Q$key\E\s*//) {
            $score += $value;
            $saw_role = 1;
            last;
        }
    }
            
    while (my ($key, $value) = each %post_attrs) {
        if ($type =~ s/\Q$key\E\s*//) {
            $score += $value;
            $saw_post = 1;
            last;
        }
    }
                  
    if (length $type || $saw_pre && $saw_post || !$saw_role) {
        # Illegal or unknown usertype.
        $score = $def_score;
    }

    $max_score = $score if $score > $max_score;
}
         
foreach my $level (@trust) {
    return $level -> [0] if $max_score >= $level -> [1];
}
            
return $def_trust;

[download]

Abigail

In reply to Re: Assigning Opsets by User Type by Abigail-II
in thread Assigning Opsets by User Type by djantzen

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.