Name Change Types & Entities

(Enum) Name Change Status

'pending', 'approved', 'denied'

Name Change Review Context

This JSON object can have many shapes, depending on the context that lead to the name change being denied or skipped. These are examples of all possible shapes:

Denied Context

{
    reason: 'manual_review';
}

{
    reason: 'old_stats_cannot_be_found';
}

{
    reason: 'new_name_not_on_the_hiscores';
}

{
    reason: 'negative_gains';
    negativeGains: {
        attack: -5867834,
        hunter: -12355,
        zulrah: -53
    }
}

Skipped Context

{
    reason: 'transition_period_too_long';
    maxHoursDiff: 504;
    hoursDiff: 596;
}

{
    reason: 'excessive_gains';
    ehpDiff: 407;
    ehbDiff: 204;
    hoursDiff: 596;
}

{
    reason: 'total_level_too_low';
    minTotalLevel: 700;
    totalLevel: 384;
}

(Object) Name Change

Field	Type	Description
id	integer	The name change's unique ID.
playerId	integer	The name change's parent player ID.
oldName	string	The player's "previous" username.
newName	string	The player's "new" username.
status	NameChangeStatus	The name change's status.
reviewContext	ReviewContext?	The name change's reason to have been denied or skipped during auto-review.
resolvedAt	date?	The date at which the name change has been approved/denied.
updatedAt	date	The date at which the name change was last modified.
createdAt	date	The date at which the name change was submitted.