- Status
- Offline
- Joined
- Mar 3, 2026
- Messages
- 754
- Reaction score
- 457
Broken interactions for Bronze and Copper Rhinos?
If you are running an EO private server and players are complaining about right-clicking their Rhino eggs with zero response, your cq_action chains are likely missing or misconfigured. This is a common oversight on older bases where premium mount logic wasn't properly templated into the egg bag system.
To bridge the item right-click to the Eudemon egg bag monster addition, you need to execute these SQL queries. I recommend running them separately to ensure no ID conflicts with your existing database structure.
Bronze Rhino Action Chain
Copper Rhino Action Chain
Testing these on a standard source shows they hold up fine. If your base IDs (4600720/4600730) are already taken, just increment them and update the id_action reference accordingly.
Post your Navicat logs if the sequence fails to trigger.
If you are running an EO private server and players are complaining about right-clicking their Rhino eggs with zero response, your cq_action chains are likely missing or misconfigured. This is a common oversight on older bases where premium mount logic wasn't properly templated into the egg bag system.
To bridge the item right-click to the Eudemon egg bag monster addition, you need to execute these SQL queries. I recommend running them separately to ensure no ID conflicts with your existing database structure.
Bronze Rhino Action Chain
Code:
-- Example base ID: 4600720
INSERT INTO cq_action (id, id_next, id_nextfail, type, data, param) VALUES
(4600720, 4600721, 0, 0508, 0, '1 0 52'), -- Check egg bag
(4600721, 4600722, 0, 0502, 729202, '1'), -- Delete egg
(4600722, 4600723, 0, 0501, 1081840, ''), -- Add bag monster
(4600723, 0, 0, 1085, 0, 'BronzeRhino Egg hatched.'); -- Log / Message
UPDATE cq_itemtype SET id_action = 4600720 WHERE id = 729202;
Copper Rhino Action Chain
Code:
-- Base ID: 4600730
INSERT INTO cq_action (id, id_next, id_nextfail, type, data, param) VALUES
(4600730, 4600731, 0, 0508, 0, '1 0 52'), -- Check egg bag
(4600731, 4600732, 0, 0502, 729203, '1'), -- Delete egg
(4600732, 4600733, 0, 0501, 1081850, ''), -- Add bag monster
(4600733, 0, 0, 1085, 0, 'CopperRhino Egg hatched.'); -- Log / Message
UPDATE cq_itemtype SET id_action = 4600730 WHERE id = 729203;
- Type 0508: Verifies the contents and availability of the Eudemon egg bag.
- Type 0502: Handles the deletion of the source item (the Rhino egg) from the inventory to prevent dupes.
- Type 0501: Executes the actual monster addition to the specific bag ID.
- Type 1085: Simulates the client-side system message confirming the hatch.
Testing these on a standard source shows they hold up fine. If your base IDs (4600720/4600730) are already taken, just increment them and update the id_action reference accordingly.
Post your Navicat logs if the sequence fails to trigger.