MVP Mob System: Ultimate Raid Scoreboard

฿3,900.00
Source Code Script
Shopping Cart Digital Delivery
Auto
View Cart View Cart and Checkout
Visited 529 times

Product Details

If you are looking for a system to change the way MVP Boss hunting works or a system to create World Bosses to add fun to your server with traditional monster hunting, take a look at this. I designed the system carefully; it is ultra-smooth, lightweight, and does not consume server resources. It can easily support large servers and is designed for highly flexible configurations. Let's take a look at the details of the mvpmob system.


Technical Data of the mvpmob Command System

Developed on: rAthena 2026

Supported: rAthena 2023+

System: Source Code + Script


Files Included When Purchasing the mvpmob System

  • mvpmob_src.patch
  • mvpmob_database.sql
  • mvpmob_core.txt - Script file responsible for receiving data from the source code, saving to the database, and defining the score calculation formulas.
  • mvpmob_scoreboard.txt - Script file for the monster hunting detail display board.
  • mvpmob_example.txt - Example file using the 2 types of mvpmob commands.
  • mvpmob_reward.yml


What does the mvpmob command do?

The mvpmob command works like regular monster spawning commands such as monster or boss_monster, but a monster summoned with mvpmob features systems for tracking damage dealt, damage taken, healing teammates, the first hit, and the final hit. These are divided into score categories and combined to rank players. Parties or players then receive rewards based on their ranks when the monster dies.


The mvpmob command is designed to spawn monsters in 2 ways


Method 1: Static spawn

// Format: <map name>,<x>,<y>,<width>,<height>    mvpmob    <name to show>    <mob id>,<delay1>,<delay2>

pay_fild10,0,0,0,0 mvpmob Eddga 1115,7200000,600000

What are [width] and [height]?

In the rAthena script system, [width] and [height] denote the "Random Radius / Bounding Box" of the monster.


To make it easier to understand, consider these 2 conditions:

1. Setting values to 0,0,0,0

pay_fild10,0,0,0,0

• Meaning: If X, Y, Width, and Height are all 0, the monster will "Random Anywhere" on the map. Similar to natural monsters, its spawn point is entirely unpredictable.


2. Setting X, Y points and providing Width, Height

pay_fild10,150,200,5,10

• Meaning: The system centers the spawn area at X=150, Y=200.

• Width (5): The monster will randomly spawn on the X-axis (left-right) up to 5 cells away.

• Height (10): The monster will randomly spawn on the Y-axis (up-down) up to 10 cells away.

• Result: The monster will spawn within a small rectangular bounding box around coordinates 150, 200. Ideal if you want a monster to spawn only within an "Arena" or "Monster Room" without leaving the boundaries.


Method 2: Spawning via script

// Format: mvpmob "<map name>",<x>,<y>,"<name to show>",<mob id>;

mvpmob "pay_fild10", 0, 0, "Eddga", 1115;

*Both methods enforce spawning 1 monster per command usage to maintain system smoothness.


Core Configurations

Open the file conf/battle/misc.conf and you will find new settings like this:

// Reward Mode: 1 = Reward only the highest scorer (Rank 1), 2 = Reward based on rank (Rank 1, 2, 3...)
mvpmob_reward_mode: 1

// Maximum number of ranks that will receive a Rank Reward (applies only if mvpmob_reward_mode: 2)
mvpmob_rank_winners: 3

// Minimum score (Damage + Tank + Heal) to prevent leeching (Anti-Leech)
// 0: Disabled (rewards everyone who hits the boss even once)
mvpmob_anti_leech_min_score: 10000

// Dynamic HP Scaling Mode (automatically increases boss HP based on the number of attackers)
// 0: Disabled (boss HP remains constant)
// 1: Enabled (boss HP increases by X% based on the number of attackers in the map)
mvpmob_dynamic_hp_scaling: 0

// Enable-Disable counting damage from player companions
// 1: Homunculus
// 2: Mercenary
// 4: Pet
// 8: Elemental (Sorcerer's summon)
// (0 = Disabled, 1=Hom, 2=Mer, 4=Pet, 8=Elem, 15=All enabled)
mvpmob_count_companion_damage: 15

First, I want to clarify why I added the settings mvpmob_reward_mode and mvpmob_rank_winners. If mvpmob_reward_mode: 1, there is only one MVP Party—the team with the highest score. If mvpmob_reward_mode: 2, there can be multiple MVP Parties, receiving rewards as configured in mvpmob_reward.yml. For participants who hunted but didn't rank, they will also receive participation rewards. I designed it so that everyone who participates, including ranked teams, receives participation rewards.


Example Reward Configuration in mvpmob_reward.yml

Open the file db/mvpmob_reward.yml to find settings for rewarding monster hunters. You can reload the reward settings with the command @reloadmvpmob

Header:
  Type: mvpmob_reward
  Version: 1


Body:
  - MobId: 1115 # Eddga
    Rewards:
      Rank 1:
        - ItemId: 501 # Red Potion
          Amount: 50
          Rate: 10000 # 100%
        - ItemId: 603 # Old Blue Box
          Amount: 5
          Rate: 5000 # 50%
        - ItemId: 5022 # Baphomet Horns (Using this as an example rare drop)
          Amount: 1
          Rate: 1000 # 10%
      Rank 2:
        - ItemId: 501 # Red Potion
          Amount: 25
          Rate: 10000 # 100%
      Rank 3:
        - ItemId: 501 # Red Potion
          Amount: 10
          Rate: 10000 # 100%
      Participation:
        - ItemId: 501 # Red Potion
          Amount: 1
          Rate: 10000 # 100%

I consider this version a base framework for anyone who likes this style. For those who want further customizations, it can be arranged (additional costs apply).


If you encounter problems, bugs, or have a poor user experience, feel free to contact me. Every piece of feedback is crucial for development.

Customer Ratings & Reviews (0 Reviews)

0.0/5
based on 0 reviews
5
0
4
0
3
0
2
0
1
0
Verified purchasers only
No reviews yet for this product

Have you used this product? Share your experience to help others make informed decisions.