RunUO Community

This is a sample guest message. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

How to use the new [freeze and [unfreeze commands

rlitt3

Wanderer
How to use the new [freeze and [unfreeze commands

Before I get started on the step by step stuff, here are a few things you need to understand:

The purpose of the new [freeze and [unfreeze commands are to move items back and forth between the static files (in UO folder) and the worldfile (in RunUO saves/items) This is so you can delete unwanted static items and to freeze items to the static files. Having most of your items in the static files can greatly reduce lag and save times.

Dynamic items are items that reside in the worldfile (in saves/items). You can have virtually any item in worldfile. The items that need to be in the worldfile and should never be frozen into statics are usable items such as doors, containers, spawners, moongates, forges, anvils, looms, spinning wheels, ovens, etc.

Static items are items that are frozen into the staticsX.mul and staidxX.mul files. The only things that should be static are decorations, building parts such as walls, floors, roofs, etc. Basically anything that has no function other than to look pretty.

It is highly recommended that you create a separate RunUO folder for the sole purpose of freezing and unfreezing stuff. The last thing you want to do is accidentally freeze all your spawners, doors, etc. If you insist on using your regular RunUO folder that you have been working on, NEVER use the [freezemap or [freezeworld commands!

1. Download the latest version of RunUO; rename it something other than your normal RunUO folder and extract to wherever you want. Open up the Saves/Items folder and delete the contents. Also delete the contents in Saves/Mobiles.

2. Create a folder called editedstatics (or whatever you want) in the UO folder (or wherever you want). Copy and paste the staticsX.mul and staidxX.mul (X = 0 for britannia, 2 for Illshenar, or 3 for Malas) from the Main UO folder to your editedstatics folder.

3. Open up datapath.cs (in Scripts/Misc.) with a text editor and look for this line:

[code:1]private static string CustomPath = null;[/code:1]

Replace null with the path to your editedstatics folder. Should look something like this :

[code:1]private static string CustomPath = @"E:\Ultima Online 2D\editedstatics";[/code:1]

The reason you have to do this is you can't edit the same statics files the client is already using.

4. Launch RunUO and the client. Now you are ready to start freezing and unfreezing. Here are the commands with descriptions :

[freeze : will bring up a targeting cursor along with a message 'target the first location of the bounding box'. Click on the NW corner of the area you want to freeze items. You will get another message and targeting cursor. Click on the SE corner of the area you want to freeze items. You can also click on a single item twice if there is only one item you want to freeze.

NOTE : The freeze command will only work on items that you add using the following command : [add static #####. Example : Use [add static 2902 instead of [add woodenchair. Will not recognize things that are added using a script.

[freezemap : will freeze all the items in the current facet you are in (felucca, trammel, illshenar, or malas) This is a good command to use if you would rather refreeze all your items at once rather than using [freeze in a bunch of different places.

[freezeworld : will freeze all the items in all facets

After freezing, you will see all the items that you froze disappear. This is because the items were deleted from the worldfile and transferred to the statics files. You will need to close client (save first), copy the statics files from your editedstatics folder to your main UO folder, and then restart client to see the changes. It is not necessary to close and relaunch the RunUO dos window.

[unfreeze : basically follow the same thing as in the [freeze command above. If you want to remove a particular item, just click on the same item twice, then do the [remove command and click on it. The item will still be there until you [save, close out client, copy the statics files from your editedstatics folder to you main UO folder, and start up client again.
Again, it is not necessary to close and relaunch the RunUO dos window.


[unfreezemap : (not recommended) will unfreeze all items in the facet you are currently in. Most likely will freeze up your computer or at least take a very long time (hours) till it finally finishes.

[unfreezeworld : (not recommended) same as above except it does all facets.

Hope this clears up some stuff. PM me if you see anything I need to change or add here or if you have further questions.
 

chunkygravy

Traveler
so when i unfreeze stuff (like walls, carpet, and trees) they should be deletable right?
when i delete them it says item deleted, but nothin happens.
do i have to copy anything to see the changes when unfreezing and deleting?
 

WillieZeke

Sorceror
so when i unfreeze stuff (like walls, carpet, and trees) they should be deletable right?
when i delete them it says item deleted, but nothin happens.
do i have to copy anything to see the changes when unfreezing and deleting?
It has been my experience that somtimes after unfreezing and deleting I did not see the deletions until i disconnected my client and reconnected. Only did i then see the changes
 

WillieZeke

Sorceror
How to use the new [freeze and [unfreeze commands

Before I get started on the step by step stuff, here are a few things you need to understand:

The purpose of the new [freeze and [unfreeze commands are to move items back and forth between the static files (in UO folder) and the worldfile (in RunUO saves/items) This is so you can delete unwanted static items and to freeze items to the static files. Having most of your items in the static files can greatly reduce lag and save times.

Dynamic items are items that reside in the worldfile (in saves/items). You can have virtually any item in worldfile. The items that need to be in the worldfile and should never be frozen into statics are usable items such as doors, containers, spawners, moongates, forges, anvils, looms, spinning wheels, ovens, etc.

Static items are items that are frozen into the staticsX.mul and staidxX.mul files. The only things that should be static are decorations, building parts such as walls, floors, roofs, etc. Basically anything that has no function other than to look pretty.

It is highly recommended that you create a separate RunUO folder for the sole purpose of freezing and unfreezing stuff. The last thing you want to do is accidentally freeze all your spawners, doors, etc. If you insist on using your regular RunUO folder that you have been working on, NEVER use the [freezemap or [freezeworld commands!

1. Download the latest version of RunUO; rename it something other than your normal RunUO folder and extract to wherever you want. Open up the Saves/Items folder and delete the contents. Also delete the contents in Saves/Mobiles.

2. Create a folder called editedstatics (or whatever you want) in the UO folder (or wherever you want). Copy and paste the staticsX.mul and staidxX.mul (X = 0 for britannia, 2 for Illshenar, or 3 for Malas) from the Main UO folder to your editedstatics folder.

3. Open up datapath.cs (in Scripts/Misc.) with a text editor and look for this line:

[code:1]private static string CustomPath = null;[/code:1]

Replace null with the path to your editedstatics folder. Should look something like this :

[code:1]private static string CustomPath = @"E:\Ultima Online 2D\editedstatics";[/code:1]

The reason you have to do this is you can't edit the same statics files the client is already using.

4. Launch RunUO and the client. Now you are ready to start freezing and unfreezing. Here are the commands with descriptions :

[freeze : will bring up a targeting cursor along with a message 'target the first location of the bounding box'. Click on the NW corner of the area you want to freeze items. You will get another message and targeting cursor. Click on the SE corner of the area you want to freeze items. You can also click on a single item twice if there is only one item you want to freeze.

NOTE : The freeze command will only work on items that you add using the following command : [add static #####. Example : Use [add static 2902 instead of [add woodenchair. Will not recognize things that are added using a script.

[freezemap : will freeze all the items in the current facet you are in (felucca, trammel, illshenar, or malas) This is a good command to use if you would rather refreeze all your items at once rather than using [freeze in a bunch of different places.

[freezeworld : will freeze all the items in all facets

After freezing, you will see all the items that you froze disappear. This is because the items were deleted from the worldfile and transferred to the statics files. You will need to close client (save first), copy the statics files from your editedstatics folder to your main UO folder, and then restart client to see the changes. It is not necessary to close and relaunch the RunUO dos window.

[unfreeze : basically follow the same thing as in the [freeze command above. If you want to remove a particular item, just click on the same item twice, then do the [remove command and click on it. The item will still be there until you [save, close out client, copy the statics files from your editedstatics folder to you main UO folder, and start up client again.
Again, it is not necessary to close and relaunch the RunUO dos window.


[unfreezemap : (not recommended) will unfreeze all items in the facet you are currently in. Most likely will freeze up your computer or at least take a very long time (hours) till it finally finishes.

[unfreezeworld : (not recommended) same as above except it does all facets.

Hope this clears up some stuff. PM me if you see anything I need to change or add here or if you have further questions.

In step 3 which datapath.cs ? the one for the new or the one for the actual server?
 
Top