Guides & documentation.

A clarification regarding antivirus detections and Themida protection.

We would like to address concerns regarding antivirus warnings that may appear when downloading or running the Pegasus MU Online client.

To protect our software, intellectual property, and proprietary development work from unauthorized modification and reverse engineering, Pegasus uses Themida, a commercial software protection solution.

Themida applies advanced executable protection techniques, which may trigger heuristic or machine-learning-based detections from certain antivirus engines.

VirusTotal Comparison

The significant difference between these results suggests that the protection process is contributing to the additional antivirus detections. However, antivirus detections should not automatically be considered false positives solely because Themida is being used.

Our Commitment to Transparency

We understand that security is important to every server owner and player.

Pegasus will continue reviewing antivirus compatibility, investigating reported detections, and improving our software distribution process.

We encourage customers to review the available scan results and contact us directly if they encounter security warnings.

Software protection is important to us, but so are transparency, customer trust, and security.

Thank you for your continued trust and support.

— Pegasus Development Team

Configure item ranks, colors, and excellent options using CustomItemRank XML.

1. Rarity levels

Ranks are defined in RankInfo using Level, Name and Color. The color IDs in the supplied XML are 0, 4, 1, 6, 13, 2 and 3 respectively.

2. Excellent options and item categories

ItemRankInfo contains options for Weapons, Shields, Helms, Armor, Pants, Gloves and Boots. Each entry specifies an item index range and an Excellent Option identifier.

<Item MinIndex="3072" MaxIndex="3180" Text="Increases Zen Drop Rate +%d %%" OptionExl="1" BaseValue="30" PlusValue="2" />

MinIndex/MaxIndex select item ranges; Text is the displayed description; OptionExl identifies the option (1, 2, 4, 8, 16 or 32); BaseValue is the starting value and PlusValue is the configured per-level increment.

3. Example shown in the tooltip

The Dazzling Armor +15 example displays Uncommon Zen Drop +32%, Rare Defense Success +8%, Epic Reflect Damage +10%, Legendary Damage Decrease +12, Mythic Maximum Mana +20% and Super Maximum Life +22%.

4. Configuration notes

Do not duplicate Rank Level values. Match item index ranges to the intended category. Save the file in UTF-8, and escape reserved XML characters such as & using &.

5. Connection to Item Server — ItemOptRank

The Item Rarity System is linked to ItemOptRank in the Item Server section. When configuring rarity options, review the ItemOptRank settings alongside CustomItemRank so the corresponding item options are configured consistently.

/Make Type Index 63 63 63 63 63 0 0 1 2 3 4 5 6

Configure account upgrade packages, bonuses, coin prices and event entry limits through PlatinumServiceInfo XML.

1. Platinum packages

2. XML configuration example

Each Platinum entry defines one package. This example uses the Daily package.

<Platinum Index="0" Name="Daily" DailyReward="No" Exp="10" Drop="10" Days="1" Coin1="5000" Coin2="100" Coin3="200" Chaosrate="5" Ware="4" BloodCastle="3" DevilSquare="3" ChaosCastle="3" Dungeon="3" />

3. Configuration fields

4. How to upgrade in game

Open the Platinum Service window, compare package prices and privileges, and select HIGHER for the desired package. Verify the account balance and package conditions before confirming.

5. Important notes

Package indices in this example are 0–2. DailyReward enables the daily reward option when set to Yes. Warehouse and event limits depend on the server implementation; review settings before applying them to a live server.

Assign one of four HP bar styles to a monster or boss using its ID in CustomHPBar.xml.

1. Four HP bar styles

Four HP bar styles presented together in one visual comparison.

2. CustomHPBar.xml configuration

Add a Boss entry with the target monster ID, HP bar Type, and MaxBar value.

<CustomHPBar>
    <Boss ID="275" Type="0" MaxBar="10" />
    <Boss ID="900" Type="1" MaxBar="10" />
    <Boss ID="42" Type="2" MaxBar="10" />
    <Boss ID="806" Type="3" MaxBar="10" />
</CustomHPBar>

3. Configuration fields

4. Adding a monster

Find the monster or boss ID, add a Boss entry inside CustomHPBar, choose Type 0–3 and MaxBar 1–10, then save the XML and verify the result in game. Follow your server’s normal configuration reload procedure.

The supplied XML uses MaxBar=10 for every entry. The exact behavior of multiple HP bars should be verified in the game.

Browse the effect files supported by Pegasus. Select a file to view its purpose and type. This is an interactive reference, not an editor for your actual server files.

CEffect.txt

All 12 files are listed below. Actual syntax and available parameters depend on your Pegasus build.

Configure the Quest interface and adjust how 3D item models appear inside the quest reward panel.

1. Quest interface

The Quest System interface displays mission objectives, progress, requirements and rewards. The quest list includes Main Quest, Event Quest, Daily Quest and Dungeon categories.

2. Client — Quest item BMD positioning

Edit Data/Local/Xml/NpcQuestItemRenderCfg.xml to adjust the scale and position of rendered quest items. These settings help align BMD models with the Quest interface.

<NpcQuestItemRenderConfig>
    <Item Type="12" Index="15" OffsetX="-4" OffsetY="0" Scale="1.0" UI="QUEST" />
    <Item Type="12" Index="137" OffsetX="0" OffsetY="4" Scale="1.0" UI="QUEST" />
    <Item Type="12" Index="30" OffsetX="0" OffsetY="5" Scale="1.2" UI="QUEST" />
    <Item Type="14" Index="141" OffsetX="5" OffsetY="5" Scale="1.2" UI="QUEST" />
</NpcQuestItemRenderConfig>

3. XML parameters

4. Server — Quest configuration

Quest system configuration is managed by NpcQuestConfig.xml on the server. The file contents were not provided, so this guide does not invent server-side XML attributes.

5. Configuration notes

Match Type and Index to the intended quest item, adjust OffsetX/OffsetY in small steps, and check Scale in-game to avoid clipping or oversized reward models. Back up the original XML before editing.

The in-game Market lets players list, browse and purchase items using supported currencies, with filters, listing history and item previews.

1. Market interface

2. Client — ItemRenderCfg.xml

Edit Client/Data/Local/Xml/ItemRenderCfg.xml to position and scale the 3D BMD item models displayed in the Market. Type and Index identify the item; OffsetX and OffsetY adjust its placement; Scale controls its display size.

3. Server — Market.xml

The Server file Data/Custom/Market/Market.xml controls market activation, supported currencies, messages, tax rates, selling limits and blocked item options. This is a short example, not the complete file.

4. Configuration notes

Review currency switches and VAT rates before enabling the Market. ConfigLimitSell controls listing limits by account level; ConfigItemBlock restricts items that may be listed. Back up the files and verify settings in-game after making changes.

The Soul System lets players allocate Soul Points to improve character attributes across four tabs.

1. Soul System overview

2. Four Soul categories

3. Configuration files — Client & Server

Important: When modifying the Soul System, edit both Client and Server configuration files so their settings stay synchronized. Back up both files before making changes.

4. Recommended workflow

Back up both XML files, edit the matching Soul System entries on Client and Server, validate XML syntax, apply the updates using your deployment process, then test all four tabs and Soul Point allocation in game.

The exact XML schema has not been provided, so this guide intentionally does not invent XML attributes or sample configuration.

Create custom combinations with required materials, Zen costs, success rates and rewards. Failed attempts can contribute a configurable bonus.

1. Custom Mix interface

2. Server configuration

GroupMix defines each recipe. ReqItemMix lists the materials, while SuccessItemMix defines possible rewards. MessageInfo contains the success and failure messages.

3. GameServer settings — Common.dat

CustomMixFailBonusRate sets the bonus rate for failed attempts; CustomMixMaxFailCount limits the number of failed attempts counted. The screenshot shows +0% (0/10) with these settings.

4. Main XML parameters

5. Configuration notes

Back up the XML and Common.dat before editing. Validate the XML and test the recipe in-game, including success, failure, costs and rewards. Exact behavior of rate fields must be confirmed in the server implementation.

Choose a dungeon and difficulty, review monster boosts and entry requirements, then start the challenge. Available dungeons shown include Nightmare's Lair, Kanturu Dungeon, Crywolf Dungeon and Karutan Dungeon.

1. Dungeon interface overview

2. Difficulty comparison — Nightmare's Lair

Values are transcribed from the four supplied in-game screenshots. All four examples show Solo mode, GR 0–0, 2/2 entries and one required item. The values may differ for other dungeons or server configurations.

3. Dungeon selection

4. Requirements and boosts

The interface displays experience rate, monster HP, damage and defense, Grand Reset (GR), Reset (RS), remaining entries and required item quantity. Check the requirements for the selected difficulty before starting.

5. Configuration notes

The Dungeon plugin may have separate configuration files depending on its release. No verified XML paths or configuration schema were provided, so this guide does not invent file names or attributes. Consult the plugin package before changing settings.

A seasonal progression system with missions, EXP, level-based rewards, and optional Premium Pass upgrades.

1. System overview

2. Server configuration

Configure the season and rewards in the following server file:

<Settings Enable="1" MaxLevel="100" SeasonDuration="180" ResetType="Season">
  <TimeConfig StartDate="2026-02-01" EndDate="2026-08-01" />
  <PremiumPass Price="5000" CoinType="WCoin" />
  <BuyLevel Enable="1" PricePerLevel="1000" CoinType="WCoin" MaxBuyPerDay="10" />
</Settings>

3. Free and Premium rewards

FreeRewards and PremiumRewards define separate item rewards for each pass level. Count, TypeItem, IndexItem, item level, durability, excellent options, sockets and other item attributes can be configured.

<FreeRewards>
  <Reward Level="1" Count="1" TypeItem="14" IndexItem="151" LvItem="0" Dur="10" Skill="0" Luck="0" Opt="0" Exc="0" Anc="0" SK1="255" SK2="255" SK3="255" SK4="255" SK5="255" SKBonus="0" HSD="0" />
</FreeRewards>

<PremiumRewards>
  <Reward Level="1" Count="1" TypeItem="14" IndexItem="152" LvItem="0" Dur="20" Skill="0" Luck="0" Opt="0" Exc="0" Anc="0" SK1="255" SK2="255" SK3="255" SK4="255" SK5="255" SKBonus="0" HSD="0" />
</PremiumRewards>

4. Daily and weekly missions

Daily missions reset at 00:00. Weekly missions reset on Monday at 00:00. Configure event participation, monster kills, item collection, and EXP rewards.

<DailyQuests ResetTime="00:00">
  <Quest ID="0" Type="0" Target="BloodCastle" Count="1" Exp="50" Description="Blood Castle" />
  <Quest ID="3" Type="1" MonsterID="700" Count="1000" Exp="100" Description="Kill 1000 Monsters" />
</DailyQuests>

<WeeklyQuests ResetDay="Monday" ResetTime="00:00">
  <Quest ID="0" Type="2" MonsterID="309" KillCount="3" ItemType="14" ItemIndex="177" CollectCount="5" Exp="1000" Description="Death King’s Bone" />
</WeeklyQuests>

5. EXP progression and buying levels

ExpTable sets the EXP required for each level. BuyLevel allows up to 10 purchased levels per day at 1,000 WCoin per level in this example.

6. Configuration notes

Back up the XML before editing. Keep season dates current, validate XML syntax, and test rewards and mission resets on a test server.

Daily Reward is a 21-day check-in system integrated with Platinum Service. Eligible VIP members can claim a configured item each day.

1. Daily Reward interface

The reward calendar contains three rows of seven days. The illustration below is a newly built interface diagram, not a cropped game screenshot.

2. VIP and character requirements

RequiredVIP=3 is the configured VIP tier. Match it with the Platinum Service VIP tier mapping on your server; the display name is not determined by this XML alone.

3. Server configuration

Edit the DailyReward.xml file in your server's Daily Reward configuration directory. The exact folder path has not been supplied.

<DailyReward>
  <Settings Enable="1" RequiredVIP="3" RequiredLevel="400"
    RequiredResets="0" RequiredLvVIPChar="0" ResetHour="0" />
</DailyReward>

4. Configure rewards (Day 1–21)

Each Reward entry specifies its day, item group and index, quantity, item level and optional item attributes. The sample below shows Day 1, Day 7 and Day 21 only.

<Rewards>
  <Reward Day="1" Count="1" TypeItem="14" IndexItem="13" LvItem="0" />
  <Reward Day="7" Count="1" TypeItem="14" IndexItem="13" LvItem="1" />
  <Reward Day="21" Count="1" TypeItem="14" IndexItem="13" LvItem="3" />
</Rewards>

These shortened Reward lines are illustrative. Keep all the original item attributes (Dur, Skill, Luck, Opt, Exc, Anc, SK1–SK5, SKBonus and HSD) when editing your actual XML.

5. System messages and claim rules

MessageInfo contains feedback for already-claimed rewards, claiming future days, success, failure, full inventory and missing VIP membership. Previous missed days cannot be claimed retroactively according to the shown interface.