1.0.2
Documentation update
This commit is contained in:
1 parent
f15ace5865
commit
110518085e
12 files changed
No files matched your search
@@ -0,0 +1,90 @@
|
||||
# Releasing Mobs
|
||||
|
||||
This guide explains how to release a mob that has been captured inside an RS-MobCage.
|
||||
|
||||
Once a mob has been captured, the filled Mob Cage can be carried to another location and used to release the mob back into the world.
|
||||
|
||||
---
|
||||
|
||||
## Before Releasing a Mob
|
||||
|
||||
Before releasing a mob, make sure:
|
||||
|
||||
- You have a filled Mob Cage.
|
||||
- You are at the location where you want the mob to appear.
|
||||
- There is enough space for the mob to spawn.
|
||||
|
||||
The filled Mob Cage contains the information needed to recreate the captured mob.
|
||||
|
||||
---
|
||||
|
||||
## Releasing the Mob
|
||||
|
||||
To release a captured mob:
|
||||
|
||||
1. Place the filled Mob Cage in your main hand.
|
||||
2. Move to the location where you want to release the mob.
|
||||
3. Use the Mob Cage to release the mob.
|
||||
|
||||
If the release is successful, the captured mob will be recreated in the world.
|
||||
|
||||
---
|
||||
|
||||
## After Release
|
||||
|
||||
After the mob has been successfully released:
|
||||
|
||||
- The mob will appear in the world.
|
||||
- The filled Mob Cage becomes an empty Mob Cage.
|
||||
- The empty cage can be used again to capture another supported mob.
|
||||
|
||||
This allows the same Mob Cage to be reused multiple times.
|
||||
|
||||
---
|
||||
|
||||
## Mob Information
|
||||
|
||||
RS-MobCages uses mob descriptors to store and restore information about supported mobs.
|
||||
|
||||
Depending on the type of mob, this may include information needed to preserve that mob's appearance or variant when it is released.
|
||||
|
||||
For more information, see:
|
||||
|
||||
➡️ [Mob Variants and Attributes](./docs/Mob-Variants-and-Attributes.md)
|
||||
|
||||
---
|
||||
|
||||
## Choosing a Release Location
|
||||
|
||||
Before releasing a mob, make sure the intended location is suitable for that mob.
|
||||
|
||||
For example:
|
||||
|
||||
- The mob should have enough physical space to spawn.
|
||||
- The release location should not place the mob inside solid blocks.
|
||||
- The area should be appropriate for the mob you are releasing.
|
||||
|
||||
If a release cannot be completed, check the surrounding area and try again.
|
||||
|
||||
---
|
||||
|
||||
## Reusing the Mob Cage
|
||||
|
||||
One of the primary purposes of RS-MobCages is reusability.
|
||||
|
||||
The same basic process can be repeated:
|
||||
|
||||
1. Capture a mob.
|
||||
2. Transport the filled Mob Cage.
|
||||
3. Release the mob.
|
||||
4. Reuse the empty Mob Cage.
|
||||
|
||||
---
|
||||
|
||||
## Returning to Capture
|
||||
|
||||
After releasing a mob, the empty Mob Cage is ready to be used again.
|
||||
|
||||
To learn more about capturing mobs, see:
|
||||
|
||||
➡️ [Capturing Mobs](./docs/Capturing-Mobs.md)
|
||||
Reference in new issue
Block a user