Magic Method Documentation

Warning

We don't recommend you learning magic method if you don't have a basic understanding of Minecraft texture pack coding and how to edit entity files.

🔮 What is Magic Method?

Magic Method is a method created by Chainsketch that allows you to exchange data in entity files in the game. The best, and the most commonly used method is temp leaking. This allows you to make many mods as magic method allows you to transfer data between other players, mobs and particles.

Note

We want to credit Chainsketch in everyway possible, so please check out his YouTube, Discord, and Twitter!

Pros and Cons of Magic Method

✅ Pros:

• You can access data from almost anywhere.
• It is relatively easy to setup once you know what you are doing.
• It is compatible with any texture pack so you can add it.
• It isn't experimental like public variables.

❌ Cons:

• Most servers have anticheats built in to stop you from accessing others data.
• It is difficult to learn.
• It will spontaneously break without much warning.

🤔 To understand Magic Method....

To understand Magic Method you have to know about the different storage types. Most often you will see variable being used but other things like temp and context exist. For magic method you need to use temp, as it directly writes to the game's storage.

| Name | Description | | --- | --- | | variable.variable_name | Read/write storage on an actor | | temp.variable_name | Read/write temporary storage | | context.variable_name | Read-only storage provided by the game in certain scenarios |

Go to your whatever.entity.json file in your workspace, if you don't already have one extract it from the base vanilla resource pack here. It is in the folder entity, and will need to put in another folder with the name of entity.

Inside the file you will want to look for pre_animation

"pre_animation": [
    "temp.my_first_mm_test = temp.my_first_mm_test ?? -1",
]

This is very important when using Temp leaking / Magic Method when the temp has no value in game storage it will set it as -1 this (if you dont do this you wont be able to test for temps in most places sense molang will just treat it as an error)

💧 Render Controller Leaks

In the render controller folder, there are many different render controllers. You can go into the folder and find a file that is linked to the player entity. Inside different attributes like the textures or overlay colors you can actually set up variables. Here is an example:

"controller.render.player.third_person": {
    "geometry": "Geometry.default",
    "materials": [
        {
            "*": "Material.default"
        }
    ],
    "textures": [
        "temp.my_first_mm_test = query.distance_from_camera; return Texture.default;"
    ],

Warning Make sure you use proper syntax. Every line must end with a ;. If you are using this in the textures area, you must add return Texture.[whatevertexture];.

Now once you assign this to value, you can use temp.my_first_mm_test as any other variable, and render things on your screen.

🌍 Example Pack

If you don't understand packs or can't understand this guide we have an example pack. This pack tells you the distance from the closest player with an iron sword. Please don't use this on Hive's Murder Mystery as this would technically be a hack.

Download Here

See Example Video

✨ Particle Leaking

This is similar to render controller leaking but this is more recommended and you can more accurately choose who you want to get data from. More coming soon....

Block Detection

If you want to be able to detect blocks around an entity with magic method you can use particles.

"minecraft:particle_expire_if_in_blocks": [
    // minecraft block names, e.g. 'minecraft:water', 'minecraft:air'
    // these are typically the same name as in the /setblock command
    // except for the minecraft: prefix
    "blockname1",
    "blockname2", 
    // So on so on...
],

Now that you have set this code up, you need to tell the particle what to do if it expires. So, you will need to write the following code:

"minecraft:emitter_lifetime_events": {
      "expiration_event": "stop"
}

This is the code that writes the value to the temp. So if it detects the block, it runs something that changes the temp value.

"stop":{
  "expression": "temp.yourtemp = 1;"
}

🌍 Example Pack Coming Soon!

Experimental Ideas

There might be a way to do Magic Method with just JSON UI. This would need you to display every single paperdoll in a game as it would show from their perspective. You can do this by changing the uuid of the paperdoll, and if you can make a grid getting all of their uuids it is technically possible.

📜 Special Credits

Documentation made by White and chyves

Edited by xStormy

Feel free to use the example pack but please do not steal it's contents and claim it as your own.