Journals
The Journal section combines project performance, player activity, and operational monitoring. Access can be granted separately for each journal group.
Use Item Monitoring to review rare game items and their holders.
Player ratings shows answers about the project, server, shop and support, their averages and history. Project cleanup can remove unanswered questions only or all ratings.
Purchase statistics compares shop, services, game currency, cases, lucky wheel and gift codes. The purchase journal provides purchase search, payment details, recipients, rewards and refunds.
Use Clan Donations to match the current clan roster with completed payments from its members.
Unique Players shows daily audience and data coverage for each game server. Bonus Balances reconciles available, consumed, and expiring grants.
Online statistics contains the latest server samples, charts, and history with explicit unavailable states. Cleaning up old samples and rating snapshots requires a separate permission.
Overview
Open Journal -> Dashboard. Select a project, game server and period, then use the refresh button beside the filters. Choose a preset or enter custom dates. The range includes both selected UTC days. The default range is the last 30 days.
The server filter applies to payments and online populations. Accounts and player activity cover the entire project. Staff actions cover the entire team and require the separate permission to view administrator logs.
The navigation above the reports moves to each section. Links at the bottom open the detailed journals available to the staff member.
Period And Detail
For an annual dashboard, choose This year, Previous year or select January 1 through December 31 of the chosen year. All sections use that period; current account counts and the latest server samples still represent their current state. Automatic detail groups annual charts by month. Future months are not filled with zeros.
There is no limit on the number of years. Enter the start and end dates for a multi-year overview. Automatic detail considers the duration and the number of compared series: days, weeks, months, years or several years per point. Available information depends on retained history; choosing an earlier date cannot recover missing records.
Use Group by to explicitly select days, weeks, months or years. Weeks start on Monday. Partial weeks, months and years at either end include only the selected dates. Grouping does not change amount totals. Unique players are calculated separately for the entire period: the same player may appear in several chart points.
A request with excessive detail does not return a truncated chart. Its message asks for a coarser interval or a shorter period; payment reports may also be narrowed to one server. Automatic selects suitable detail. The period and grouping survive a page refresh.
Players
Current accounts shows the project's current master-account population, regardless of the selected dates. Registered in period and the chart use the registration dates of those accounts. Chart detail follows the selected period; grouping does not change the registration total. Without registration date identifies accounts that cannot be assigned to a day: they remain in the population total but not in the registration chart.
Activity And Retention
Successful logins counts cabinet logins within the selected dates. Players who signed in counts each player once even if they signed in repeatedly. The 24-hour, 7-day and 30-day cards count unique players in the respective rolling windows; their end time appears below the cards.
New players: first 30 days examines registrations in the selected period. Percentages include only players whose first 30 days have ended and whose observation history is confirmed. Players still being observed and those without confirmed history are listed separately.
The outcomes are signing in, making at least one payment and making more than one payment within the first 30 days. Automatic sign-in after registration also counts. These are independent outcomes, not sequential steps: a payment does not require a preceding return login.
Return after registration checks for a login in the 24-hour window starting 1, 7 or 30 days after registration. For example, D1 spans hours 24 to 48. Its percentage becomes available after that window ends and only with complete history. Without eligible observations, the report shows Not available, not 0%.
Payments
This section includes completed top-up and purchase payments for the selected project and server. Test payments are excluded. When several currencies are present, select each separately; different currencies are never added together.
The selected currency shows the payment amount, payment fees, amount after fees, payment and payer counts, guest payments, top-ups and purchases. The average per payer excludes guest payments. Purchase payment count is not an order count.
Amounts reflect payment completion before subsequent refunds and disputes; they do not represent net profit. A server breakdown appears below the chart. Expand Amounts by period to inspect the intervals of the selected grouping. Payer counts from separate intervals must not be added together: the same player may have paid repeatedly.
When no eligible payments were recorded, the section displays a distinct empty state. A history warning remains visible when completeness is not confirmed.
Online
Each server shows its actual online population, available character and clan counts, and the timestamp and state of its latest measurement. Stale samples remain labelled. A missing measurement or unsupported count is not replaced with zero.
The chart shows the measured average separately for each server. Measurements taken at different times are not added into a current combined population. Detailed history and additional filters are available in Online statistics.
Selecting one server narrows this section to that server. Account and player-activity figures continue to cover the entire project.
Staff Actions
This section shows recorded actions, active team members, a chart at the selected detail and the most frequent actions within the selected dates. Switching projects or servers does not narrow these team-wide figures. Staff without permission to view administrator logs cannot see the section.
Refresh And Availability
An open page refreshes approximately every 30 seconds. Editing filters pauses automatic refresh until the filters are applied. Each section also has its own refresh button.
New events can take time to appear. A partial-history warning means that the recorded values may not represent the full period. Each section shows its update time; activity also lists the start of confirmed history.
When some data is unavailable, the affected sections display an error instead of stale figures or zero values. Other available sections continue working. Once availability is restored, refresh manually or wait for the next automatic refresh.