Master Texture HUD

The Master Texture HUD is a professional, fully functional texture changer HUD powered by the Master Menu PRO and the Master Changer PRO. The Master Menu PRO and Master Changer PRO are sold separately and not included (only a no-transfer version is included).

You get a fully functional HUD and Object. Both come with a full-perm _Config script that you can edit. The config script contains all necessary configuration values for the Master Menu PRO, Master Changer PRO and contains some extra code.


The HUD contains 6 texture/color buttons, a “minimize/maximize” button, 5 social buttons and a Delete scripts button that opens a blue dialog menu. You can of course create your own layout and add as many buttons as you want.

The 6 texture/color buttons are configured using the Master Menu PRO Config.

The buttons (prims) contain the same name as in the scripts menu config. This causes the Master Menu PRO to respond when one of the buttons is clicked.

So when for example the red button is clicked (prim name “menu:Color:Red”) the script will run “menu:Color:Red = msg,link | mc_color # A1 # <1,0,0> # -1”.

MC_COLOR is a Master Changer PRO command. You can change this to MC_TEXTURE or any other command that you want to use. You can also use multiple commands. If you for example would like to change the color and texture with one button you would do this:
“menu:Color:Red = msg,link | mc_color # A1 # <1,0,0> # -1”,
“menu:Color:Red = msg,link | mc_texture # A1 # 71449642-c5b1-ca2c-3577-7557a0db7c90 # -1”

Like the buttons the “Delete scripts” button that opens a blue menu is setup the same way. The only difference is that the button (prim) opens a blue dialog menu that then runs MC_KILL when “Yes” is pressed.

There is a lot more in the config and there are many more Master Changer PRO commands. So before continuing make sure to have a look at the Master Menu PRO Manual and the Master Changer PRO Manual.

Inside the touch_start event you can find the code that takes care of the social buttons.

Just like with the color/texture buttons the script has been setup to work based on prim names.
So if a prim with the name “www” is clicked the script sends a linked message to the Master Changer PRO: llMessageLinked(LINK_THIS, link_number, “mc_url # “+clicker+” # Visit #”, “”);

In addition to that the script contains a button effect function btn(). This plays a sound and makes the button “animate”.

The “Minimize – / Maximize +” button works the same as the “www” button as its the Master Changer PRO that takes care of the movement. The only important thing here is that your root prim is centered on the “minimize/maximize” button (as the object rotates based in the root axis).

The black box in the picture above (highlighted in yellow) is the root prim of the HUD and it is centered on the “+/- button”.

There is quite a lot of more code in the script but this generally doesn’t need to be changed. You can change it if you know what you are doing. I tried to keep the code as simple as possible however if you are having any issues or need something changed feel free to contact me.

The Object

There isn’t much you need to do in the Object script apart from setting the Communication Settings to match those of the HUD as the script has been setup in such a way that everything comes from the HUD.

The included object is only a example. You are expected to take out the scripts and put them in your own objects like for example clothes, furniture, etc.

Do note that the prim that is changing is not the root prim and that its called “A1”. Also note that the root prim is inside of the other prim.

In the HUD we have the line “menu:Color:Red = msg,link | mc_color # A1 # <1,0,0> # -1”. This line tells the Master Changer PRO to change the color of prim A1 to <1,0,0>.
It is highly recommended to use prim names instead of prim numbers as they are more reliable and don’t change every time you re-link a object.

The reason you may want to put the root prim (the black box) inside of your object is to prevent the mouse pointer to show as “touch”. You may also add the scripts in a other prim as it doesn’t matter if they are in the root prim or not.

Click to

Its not necessary but looks much nicer to only have the mouse pointer change to “Touch” when it is hovering over a button and not on the whole object.

Since you cant set the root prim to “Click to: None” we position the root prim behind the HUD. Then we set the white background and logo to “Click to: None” and make sure the buttons are set to “Click to: Touch”. This way the mouse pointer will only change to “Touch” when we are hovering over one of the buttons.

Limitless HUD

The HUD is setup so that the textures etc are send from the HUD to the object. It however does not need to be like this. I have set it up like this because i find it the most practical way as you end up only having to edit the HUD script and not both scripts.

You can edit/modified all the relevant code so there are practically no limits to what the HUD can do. The Master Changer PRO and the Master Menu PRO take care of the “complicated” scripting part.

Extra Examples

In addition to the standard HUD i have added a few other (fully working) examples that add more functions to the HUD.

Master Texture HUD (Group)
This version contains a group only button. This lets you setup a buttons that only works for group members.

Master Texture HUD (Web)
This version uses the Master Web PRO to load a button from a remote server. Note that you need both the Master Web PRO and a remote server for the data you want to load.

Custom Work

Need something specific or simply have no clue how to edit the script to get what you want? Then don’t hesitate to contact me.

Since the Master Scripts takes care of almost everything, making a HUD that does what you want is “easy” and often very little work. This also means that a custom HUD created using the Master Scripts would cost you a fraction of what a full custom script would cost and it can be done in matter of minutes.