Chapter 8 - Revision history

Soulless: /* InsideUO */

2022-08-15T12:07:24Z

‎InsideUO

Sirius: Added languagemenue

2010-11-26T20:18:25Z

Added languagemenue

MrSugarCube at 18:29, 3 June 2009

2009-06-03T18:29:12Z

MrSugarCube at 11:25, 2 June 2009

2009-06-02T11:25:06Z

Show changes

MrSugarCube: /* Gumps */

2009-06-02T10:24:39Z

‎Gumps

MrSugarCube at 09:59, 2 June 2009

2009-06-02T09:59:32Z

Show changes

MrSugarCube at 09:15, 2 June 2009

2009-06-02T09:15:33Z

MrSugarCube at 09:10, 2 June 2009

2009-06-02T09:10:19Z

MrSugarCube at 06:49, 2 June 2009

2009-06-02T06:49:05Z

MrSugarCube: Created page with '==Skill Menus== One of the most common requests by newbie admins is the ability to create new things via the craft skills. I've noticed that it is also one of the first things th...'

2009-06-02T06:48:49Z

Created page with '==Skill Menus== One of the most common requests by newbie admins is the ability to create new things via the craft skills. I've noticed that it is also one of the first things th...'

New page

==Skill Menus==
One of the most common requests by newbie admins is the ability to create new things via the craft skills. I've noticed that it is also one of the first things that players check out about a shard. If your shard has awesome craftable items, chances are the player will stick around longer and gain skill so he can see them. Craftable houses are the ultimate in cool. And this section will show you how to make one. First, we'll just look at how the crafting system works.

There are about 9 built-in section names, for each of the various crafting skills. This script is called from within the server, and if those sections don't exist, you will receive many scary errors. Here is the list, which I grabbed from the top of sphereskill.scp.

<spherescript>// Hard coded ref names: (called directly form server)
// sm_alchemy = dclick on alch tools
// sm_summon
// sm_polymorph = polymorph menus
// sm_cartography = dclick on blank map
// sm_bowcraft = knife on wood
// sm_bolts = dclick on arrows or shafts
// sm_blacksmith = dclick on tool
// sm_carpentry = dclick on carp tool
// sm_tailor_leather = dclick on sewing kit
// sm_tailor_cloth
// sm_tinker = dclick on tinker tools.
// sm_inscription = dclick on blank scroll
// sm_cook = ??? NOT USED YET</spherescript>

Here is the syntax of a SKILLMENU section, like every other section in a SPHERE script:

<spherescript>[SKILLMENU sm_alchemy]</spherescript>

Now, a skill menu is the little box that pops up that contains the pictures of the items that you can scroll through and select. There are several attributes of this box which obviously need defined. The first is the title. It goes immediately underneath the [SKILLMENU] tag.

<spherescript>[SKILLMENU sm_alchemy]
What sort of potion do you want to make?</spherescript>

That line will be displayed across the top of the menu, as the title. In the case of the alchemy skill, we simply want to ask the user what type of potion he wishes to make. The next parts of the script are a little shaky, and contain some new constructs that you may or may not recognize. In reality, it's just a series of events, which occur depending on which menu item the user picks. Here's the part of the rest of the alchemy script:

<spherescript>[SKILLMENU sm_alchemy]
What sort of potion do you want to make?

ON=i_potion_Agility <name> (<resmake>)
MAKEITEM=i_potion_Agility

ON=i_potion_AgilityGreat <name> (<resmake>)
MAKEITEM=i_potion_AgilityGreat

ON=i_potion_CureLess <name> (<resmake>)
MAKEITEM=i_potion_CureLess

ON=i_potion_Cure <name> (<resmake>)
MAKEITEM=i_potion_Cure

ON=i_potion_CureGreat <name> (<resmake>)
MAKEITEM=i_potion_CureGreat

ON=i_potion_ExplosionLess <name> (<resmake>)
MAKEITEM=i_potion_ExplosionLess

ON=i_potion_Explosion <name> (<resmake>)
MAKEITEM=i_potion_Explosion

ON=i_potion_ExplosionGreat <name> (<resmake>)
MAKEITEM=i_potion_ExplosionGreat

ON=i_potion_HealLess <name> (<resmake>)
MAKEITEM=i_potion_HealLess</spherescript>

As you can see, we still use the ON= event construction for these menus as well. The different is what follows. Let's dissect it:

<spherescript>ON=i_potion_HealLess <name> (<resmake>)</spherescript>

This line tells the server a number of things. The first parameter, immediately following the = sign, is the ID of the item to display. So, what will be displayed here is the DISPID of the i_potion_HealLess item. It happens to be a yellow potion. As soon as you specify this item, it becomes the default item for the rest of that line. The server knows that <tt><NAME></tt> refers to the name of the potion item, and that <tt><RESMAKE></tt> is a string which tells what it takes to make that item. Both of those are specified in the script for i_potion_HealLess (which is in sphere_item_provisions_potions.scp) and can easily be changed there (looks for NAME= to change the name and SKILLMAKE= to change the skill and difficulty).

<spherescript>MAKEITEM=i_potion_HealLess</spherescript>

Well if this isn't obvious, you shouldn't be reading this chapter. It simply begins the construction of the specific item. Wait, you may be asking, how does the server know which skill to use or how much skill is required, or even what to consume (1 empty bottle) when creating this item. Well, I'm glad you asked. To answer that, we need to look at the script for the item we're constructing. Ah, here it is....

<spherescript>[ITEMDEF i_potion_HealLess]
NAME=Lesser Heal
ID=i_bottle_YELLOW
RESOURCES=i_reag_ginseng, i_bottle_EMPTY
SKILLMAKE=ALCHEMY 0.1
TYPE=T_POTION
TDATA1=i_bottle_empty

ON=@Create
MORE1 = s_heal
MORE2 = 50.0</spherescript>

The two important lines are the '''RESOURCES''' and '''SKILLMAKE''' lines. These two lines work with the skill system to tell SPHERE what items are used to make this item. Basically, it says that when you create the item, you need 1 i_reag_ginseng and 1 i_bottle_empty. Incidentally, if you don't have the resources to make an item, it won't even appear on the list when you look at the SKILLMENU in-game. The next line tells the server which and how much skill is required to make this item. In this case, it says we need 0.1 in the alchemy skill. It IS just a lesser heal, after all.

Take your new i_potion_HealLess to a store and try to sell it. Magically, it seems to have a price. Where did that price come from? Well, it came from the RESOURCES. The value of a lesser heal potion is the combined value of the i_reag_ginseng and the i_bottle_EMPTY. Both of these are defined in sphere_item_resources.scp. This brings us to a point so important, I am going to put it in bold: '''An item MUST have either a VALUE or resources with a VALUE, or it will not appear in a SKILLMENU!''' Many newbie scripters ask on the boards about why their item is not appearing in an otherwise perfect SKILLMENU section. It has nothing to do with the SKILLMENU. Look at your item scripts before whining to us on the boards.

Another important point is this: You may have any number of lines between ON= events in a [SKILLMENU] section. It just happens that MAKEITEM does everything for us that we need it to do, so most scripts only have one line. However, you could print out a SYSMESSAGE or KILL a player within a SKILLMENU, just as easily as you could do it in any other event.

Now that we know this fact, let's build that craftable house I was referring to! First, we need to figure out what sort of RESOURCES we might want to use to craft a house. I would say a large amount of wood, maybe some metal for a doorknob, a deed to write on, and some magic just for the heck of it. We'll take a resources like that looks like this:

<spherescript>RESOURCES=1000 i_board, 100 i_ingot_iron, 5 i_reag_garlic, i_deed</spherescript>

We also need a SKILLMAKE definition, and for this we'll use the Carpentry skill. Say, 95.0. Then we'll put those lines into the ITEMDEF for the deed we want to make craftable:

<spherescript>[ITEMDEF i_craftable_deed]
ID=i_deed
NAME=Deed to a Small Stone House
RESOURCES=1000 i_board, 100 i_ingot_iron, 5 i_reag_garlic, i_deed
SKILLMAKE=CARPENTRY 95.0

CATEGORY=Provisions - Deeds
SUBSECTION=House Deeds
DESCRIPTION=Small Stone House

ON=@Create
MORE1 = i_multi_house_stone_small</spherescript>

This, if you haven't figured it out, is a copy of item 04202, which has been renamed and edited. You can find the original script in sphere_item_deed.scp. Now, our item has a SKILLMAKE definition, and a VALUE definition (through the RESOURCES). It is craftable. We need to stick it into one of the existing Carpentry [SKILLMENU] sections now. Let's look at one of them:

<spherescript>[SKILLMENU sm_carpentry]
Carpentry

ON=i_board boards
MAKEITEM=i_board

ON=i_chair_throne Chairs
SKILLMENU=sm_wood_chairs

ON=i_chest_wooden_brass Containers & Shields
SKILLMENU=sm_wood_containers_shields

ON=i_table_nightstand Table
SKILLMENU=sm_wood_tables

ON=i_staff_gnarled Weapons & Tools
SKILLMENU=sm_wood_weapons_tools

ON=i_armoir_dk Furniture
SKILLMENU=sm_wood_furniture

ON=i_portrait_7 Paintings
SKILLMENU=sm_wood_paintings

ON=i_trophy_deerhead Trophies
SKILLMENU=sm_wood_trophies

ON=i_saddle Rancher Types
SKILLMENU=sm_wood_rancher

ON=i_BED_9 Beds
SKILLMENU=sm_wood_beds

ON=i_bulletin_board Miscellaneous
SKILLMENU=sm_wood_misc</spherescript>

Like I said earlier, you can have any lines after an ON= section. In this case, it just happens to be a SKILLMENU line which opens up another menu. This is a hierarchical menu, because you choose from upper menu options like these, and go through lower menus, until you finally reach an item you can craft. Now, we're going to add the following two lines to the end of this script:

<spherescript>ON=i_craftable_deed <name> (<resmake>)
MAKEITEM=i_craftable_deed</spherescript>

Guess what? We're done. That's all you need to do. Now, in most cases, you would make a new [SKILLMENU sm_houses] or something similar, and then add all of your items to that. In that case, the line you'd add to the main Carpentry menu (or one of the submenus) is the following:

<spherescript>ON=i_deed Craftable Houses
SKILLMENU=sm_houses</spherescript>

That's all. Easy, isn't it? It's one of the easiest things to script, and one of the coolest. Unfortunately, it is so easy and repetitive that it takes FOREVER to make a good crafting system. If you are going to create one for your shard, start now. You should be finished in about a month. :)

@@ Line 236: / Line 236: @@
-==InsideUO==
+==UOFiddler==
-UO comes with almost 4000 gumps. You aren't going to want to try each one in a script until you figure out which is which. You're going to need some sort of a program that shows you the gump. That program is InsideUO, which has come to be as useful to SPHERE scripting as a sword to a warrior. Here's a link to download it:
+UO comes with almost 4000 gumps. You aren't going to want to try each one in a script until you figure out which is which. You're going to need some sort of a program that shows you the gump. That program is UOFiddler, which has come to be as useful to SPHERE scripting as a sword to a warrior. Here's a link to download it:
-[http://uo.stratics.com/heptazane/insideuo/index.shtml Download InsideUO]
+[http://uofiddler.polserver.com/ Download UOFiddler]
@@ Line 255: / Line 255: @@
-'''Note:''' InsideUO is a popular tool for viewing the contents of the UO files but it is not the only one out there. Check out the [[Third Party Tools]] page for a list of other programs which you may want to use.
+'''Note:''' UOFiddler is the most popular tool for viewing the contents of the UO files but it is not the only one out there. Check out the [[Third Party Tools]] page for a list of other programs which you may want to use.
 ==Gumps==

← Older revision		Revision as of 20:18, 26 November 2010
Line 1:		Line 1:
		+	{{Languages\|Chapter_8}}
		+
	==Skill Menus==		==Skill Menus==
	One of the most common requests by newbie admins is the ability to create new things via the craft skills. I've noticed that it is also one of the first things that players check out about a shard. If your shard has awesome craftable items, chances are the player will stick around longer and gain skill so he can see them. Craftable houses are the ultimate in cool. And this section will show you how to make one. First, we'll just look at how the crafting system works.		One of the most common requests by newbie admins is the ability to create new things via the craft skills. I've noticed that it is also one of the first things that players check out about a shard. If your shard has awesome craftable items, chances are the player will stick around longer and gain skill so he can see them. Craftable houses are the ultimate in cool. And this section will show you how to make one. First, we'll just look at how the crafting system works.

← Older revision		Revision as of 18:29, 3 June 2009
Line 661:		Line 661:

	It's pretty simple and with a bit of playing around you should get this to work easily. Good luck!		It's pretty simple and with a bit of playing around you should get this to work easily. Good luck!
		+
		+	[[Category:Tutorials]]

← Older revision		Revision as of 10:24, 2 June 2009
Line 431:		Line 431:

	Thus ends the first section on gumps and dialogs (which are the same thing). With this information you should be able to make just about any sort of gump you want, by playing with text and button positions. The possibilities are almost endless, and after you read Part 2, they will be endless. I have only used the information you will read in Part 2 twice in my entire long scripting career.		Thus ends the first section on gumps and dialogs (which are the same thing). With this information you should be able to make just about any sort of gump you want, by playing with text and button positions. The possibilities are almost endless, and after you read Part 2, they will be endless. I have only used the information you will read in Part 2 twice in my entire long scripting career.
		+
		+
		+	===Part 2===
		+	You've survived the first part of dialog scripting, and you're well on your way to designing some spectacular gumps I'm sure. OSI has provided us with a huge array of gumps, any of which you may use in your scripting. You might be surprised to see that all of the clothing and paperdoll type items are gumps and are listed with the others in InsideUO (at the bottom). There's even a leather dominatrix type uniform in there, and a whip, but that doesn't seem to have ever been used in UO as an item. Too bad.
		+
		+
		+	As you know, no form would be complete without text-boxes to fill in, checkboxes to click, and radio buttons to select from. There is no shortage of gump IDs to use for these purposes, but most of them don't really fit on a normal gump (because they were made for other purposes). What I like to do is use a different background than the one we were using, and then stretch ANOTHER resizepic of the type we were using over top of the first one. Here, look at this example from my messaging system to see what I mean:
		+
		+
		+	<tt><font color="darkblue">page 0<br />
		+	resizepic 0 0 5100 640 170<br />
		+	resizepic 15 155 5100 175 40<br />
		+	button 100 161 <eval g_btn_gray_apply> <eval g_btn_gray_apply_press> 1 0 901<br />
		+	button 20 161 5200 5201 1 0 900<br />
		+	text 5 10 1152 1</font><br />
		+	<font color="darkgreen">resizepic 5 30 2620 600 35<br />
		+	textentry 15 36 600 20 1152 1 0 // 4 text fields now</font><br />
		+	<font color="darkred">resizepic 5 57 2620 600 35<br />
		+	textentry 15 63 600 20 1152 2 0</font><br />
		+	<font color="yellow">resizepic 5 84 2620 600 35<br />
		+	textentry 15 90 600 20 1152 3 0</font><br />
		+	<font color="orange">resizepic 5 111 2620 600 35<br />
		+	textentry 15 117 600 20 1152 4 0<br /></font></tt>
		+
		+
		+	Don't worry about the name or the TEXT and BUTTON sections. Notice that I have constructed a rather odd gump here. As you can see, for each textentry object, I have another resizepic object. Put this in a script (with the appropriate header tags) and look at it to see what it does.
		+
		+
		+	Look carefully at the coordinates, widths, and heights of each highlighted part. If you're going to use this method, there is a particular place that you must position each so the text doesn't overlap other parts of the dialog when the player begins typing. That is called an offset. If one object is at (5, 30), and another is at (15, 36), that is an offset of (10, 6). I've discovered that the (10, 6) offset works well for space between the gold-bordered background and a textentry object.
		+
		+
		+	<spherescript color="darkgreen">textentry <x> <y> <gump width> <gump height> <color> <index> <text id></spherescript>
		+
		+
		+	Anyways, notice that the text id of each textentry field is 0. By default, the textentry field will be filled with whatever text id you give it. The player would then have to erase that to type something new, and that gets irritating. So, that's why I made the <VAR.BLANKLINE> be text id 0. There is nothing in the box when it appears, which is handy. See? There is rhyme to my reason, you just have to wait a while to get it.
		+
		+
		+	You can also use <tt>dtextentry</tt>, which acts similar to dtext and doesn't require something under the TEXT section. See below for an example.
		+
		+
		+	Now, when your gump returns, you're going to get a lot of data from each of those textboxes. Notice how each of them have an index? SPHERE has provided us with a nice variable array (yes, a REAL array) called ARGTXT which contains all of the text returned. You use <tt>ARGTXT[x]</tt> to refer to the text from textentry index x. Here is a full dialog example (actually it's the same one as above, but with some modifications).
		+
		+
		+	<spherescript>[DIALOG d_test_textentry]
		+	page 0
		+	resizepic 0 0 5100 640 170
		+	resizepic 15 155 5100 175 40
		+	button 100 161 <eval g_btn_gray_apply> <eval g_btn_gray_apply_press> 1 0 901
		+	button 20 161 5200 5201 1 0 900
		+	text 5 10 1152 1
		+	resizepic 5 30 2620 600 35
		+	textentry 15 36 600 20 1152 1 0 // 4 text fields now
		+	resizepic 5 57 2620 600 35
		+	textentry 15 63 600 20 1152 2 0
		+	resizepic 5 84 2620 600 35
		+	textentry 15 90 600 20 1152 3 0
		+	resizepic 5 111 2620 600 35
		+	dtextentry 15 117 600 20 1152 4 // using dtextentry, you can ommit the text or add some as you wish.
		+
		+	[DIALOG d_test_textentry TEXT]
		+	<VAR.BLANKLINE>
		+	Enter the message you wish to send.
		+
		+	[DIALOG d_test_textentry BUTTON]
		+	ON=901 // The apply button
		+	SRC.SYSMESSAGE You type <ARGTXT[1]> in textentry index 1!
		+	SRC.SYSMESSAGE You type <ARGTXT[2]> in textentry index 2!
		+	SRC.SYSMESSAGE You type <ARGTXT[3]> in textentry index 3!
		+	SRC.SYSMESSAGE You type <ARGTXT[4]> in textentry index 4!
		+	RETURN 0 // Yes, you can have RETURNs in a dialog</spherescript>
		+
		+
		+	This script should work fully. I did remember something while I was typing it, so I'll tell you now. The client depends on the information being sent by SPHERE, which you provide in your script, especially with the [DIALOG TEXT] section. If you refer to a text id that is not there, your client WILL crash. It is easier to crash a client with dialogs than anything else in the game. On my old server, if there was a player I didn't like, I would put an event on his character so a client-crashing gump would appear every time he logged in, no matter what. The GMs used to go crazy trying to fix that. :)
		+
		+
		+	My example should help you understand the syntax of getting data from a textentry box. Now you can make forms rather than just still-life dialogs. Remember, you don't need the resizepic background, because a textentry will work no matter what. It just helps the player know where to type.

← Older revision		Revision as of 09:15, 2 June 2009
Line 233:		Line 233:

	That's about all it takes to make a menu. Of course, you can put any commands you want after the ''ON='' section, and there can be much more than one line. In fact, for most menus, there will be. That was easy, wasn't it? :)		That's about all it takes to make a menu. Of course, you can put any commands you want after the ''ON='' section, and there can be much more than one line. In fact, for most menus, there will be. That was easy, wasn't it? :)
		+
		+
		+	==InsideUO==
		+	UO comes with almost 4000 gumps. You aren't going to want to try each one in a script until you figure out which is which. You're going to need some sort of a program that shows you the gump. That program is InsideUO, which has come to be as useful to SPHERE scripting as a sword to a warrior. Here's a link to download it:
		+
		+
		+	[http://uo.stratics.com/heptazane/insideuo/index.shtml Download InsideUO]
		+
		+
		+	It's a zip file so you need WinZip or a similar tool to extract it. Unzip it to your main SPHERE directory (where SphereSvr.exe is). If you are running a Linux server, just unzip it to somewhere on your Windows computer. It doesn't run in Linux, sorry. Now, when you run the program, you will need to enter the paths of your MUL files. In most cases, that's your the folder where you installed UO (hopefully). Go to the View menu and select File Paths. Sometimes, it will automatically detect the location of your files, in which case you don't have to do anything.
		+
		+
		+	Now, click on the GUMPS button along the sidebar and wait for it to load the index file. It will have a huge list of gumps from 00000001 to some other large number. Look down through them, write some interesting ones down, because you won't want to search back through the list every time you need a specific gump ID.
		+
		+
		+	Also, you're going to be needing backgrounds, which come in 9 parts. I'll explain that when we get there, but if you see a series of items, which look like they'd fit together, write that down, because it would make an excellent background.
		+
		+
		+	One more thing to note before we move on to the next section: The gump IDs you see here are in HEXADECIMAL. SPHERE will only accept gump IDs in decimal. This is one of those times when you need to break out the Windows Calculator and do some conversions.
		+
		+
		+	'''Note:''' InsideUO is a popular tool for viewing the contents of the UO files but it is not the only one out there. Check out the [[Third Party Tools]] page for a list of other programs which you may want to use.

← Older revision		Revision as of 09:10, 2 June 2009
Line 185:		Line 185:

	That's all. Easy, isn't it? It's one of the easiest things to script, and one of the coolest. Unfortunately, it is so easy and repetitive that it takes FOREVER to make a good crafting system. If you are going to create one for your shard, start now. You should be finished in about a month. :)		That's all. Easy, isn't it? It's one of the easiest things to script, and one of the coolest. Unfortunately, it is so easy and repetitive that it takes FOREVER to make a good crafting system. If you are going to create one for your shard, start now. You should be finished in about a month. :)
		+
		+
		+	==Menus==
		+	If you paid attention in the previous section, this section should be very simple for you. It is so much easier to make a simple menu than a skillmenu. And, when you see how to read from buttons in a GUMP, you will see how similar it is to this. Basically, in SPHERE, there are occasions when you may want to bring up a menu for the user to choose from. Say, when they choose the "Help Desk from Hell" option on your help menu.
		+
		+
		+	Do that. Right now. See how a menu pops up and asks if the user really wants to go to the help desk from hell? He can choose Yes, or No, and something different will happen in each case. Here's what the script for that menu might look like:
		+
		+
		+	<spherescript>[MENU m_helpdesk]
		+	Do you REALLY want to go to the Help Desk from Hell? You will be stuck until a GM comes to free you!
		+
		+	ON=0 Yes
		+	SRC.GO Help Desk from Hell
		+
		+	ON=0 No
		+	SRC.SYSMESSAGE Help request cancelled.
		+
		+	ON=0 I'm a monkey. Kill me.
		+	SRC.KILL</spherescript>
		+
		+
		+	It looks awfully familiar, doesn't it? Here's what each part does. (I'll only take the first four lines, because the next ones are self-explanatory if you understand the first four.
		+
		+
		+	'''[MENU m_helpdesk]'''<br />
		+	This is rather obvious. In a script, you would call this menu like this:
		+
		+
		+	<spherescript>MENU m_helpdesk</spherescript>
		+
		+
		+	Difficult eh? :)
		+
		+
		+	'''Do you REALLY want'''...<br />
		+	Like the skillmenu, this is the title of this section. The next thing I am about to discuss will determine where it is displayed.
		+
		+
		+	'''ON=0 Yes'''<br />
		+	Aha, this is the new part. Remember what the first parameter to this section in a [SKILLMENU] was? Well, it's the same thing. That is the ITEM ID that the menu is supposed to display. However, we don't want a scrolling item-based menu, but rather a menu where we can select an option from a list. When you put a 0 for the ITEM ID, SPHERE will automatically assume that you want to create a text-based MENU. However, the catch is, you must put 0 for EVERY SINGLE OPTION in your menu, or else you will get a scrolling item menu like a SKILLMENU. In our case, we want to give the user options in text format, because our menu wouldn't make much sense with scrolling items for its purposes.
		+
		+
		+	'''SRC.GO Help Desk of Hell'''<br />
		+	You know what this does. I just want to point out that the user of the menu is SRC, and the default object is whatever the MENU was called upon.
		+
		+
		+	That's about all it takes to make a menu. Of course, you can put any commands you want after the ''ON='' section, and there can be much more than one line. In fact, for most menus, there will be. That was easy, wasn't it? :)

← Older revision		Revision as of 06:49, 2 June 2009
Line 1:		Line 1:
		+	'''''(WIP)'''''
	==Skill Menus==		==Skill Menus==
	One of the most common requests by newbie admins is the ability to create new things via the craft skills. I've noticed that it is also one of the first things that players check out about a shard. If your shard has awesome craftable items, chances are the player will stick around longer and gain skill so he can see them. Craftable houses are the ultimate in cool. And this section will show you how to make one. First, we'll just look at how the crafting system works.		One of the most common requests by newbie admins is the ability to create new things via the craft skills. I've noticed that it is also one of the first things that players check out about a shard. If your shard has awesome craftable items, chances are the player will stick around longer and gain skill so he can see them. Craftable houses are the ultimate in cool. And this section will show you how to make one. First, we'll just look at how the crafting system works.