Easy to use LocalPath objects (Wishlist)

Easy to use LocalPath objects // Wishlist

1  |  

bastillion

Jan 24, 2006, 1:08pm
I think it would be a fairly easy thing to incorporate, but at the same
time, I understand what could occur.

Within the registry for AW Prime (world AW), would it be possible to add
generic item names that people could then create local versions of their own
objects that would appear only in their browser?

Let me explain a bit better my idea:

I found a few objects I would like to use in world AW and then renamed them
after the "x0" objects (which are the playing card objects). While in my
localpath, whenever the browser comes across a card object that I have
replaced, instead of loading the small card, it instead loads the object
from my localpath.

For example, I renamed one of Kitiara's Cabins "x0d.cob", zipped it into
"x0d.zip", and then placed it into my localpath. Now, whenever I come
across that object, instead of seeing a small playing card, I see her custom
cabin.

Granted, anyone else that comes into the area still only sees the stray
playing card, but if they were to put my renamed x0d.zip into their
localpath and enable use of the localpath, then they would also see the
cabin.

Example here:
http://bastillion.net/img/AWE-examples/x0d-standard.gif <---what standard
AW user sees
http://bastillion.net/img/AWE-examples/x0d-bastmod.gif <---renamed objects
in localpath

http://bastillion.net/img/AWE-examples/xobjects-standard.gif <---cards
out in a field
http://bastillion.net/img/AWE-examples/xobjects-bastmod.gif <---becomes a
carousel when objects renamed!

Now, I understand that AWI would prefer people to purchase their own worlds
and develop their own object paths, but what about the userbase that cannot
afford to do that? Why limit their creativity if they could make an area in
the massive public world AW where they could share their objects with
friends/visitors to their area?

My suggestion would be to set aside these generic object names in the
registry for people to use:

lp(1-X).rwx where X can be decided.. perhaps even something like
lp001.rwx, lp002.rwx, lp083.rwx... you get the idea.

Granted, with such generic names, the person using their localpath would
have to remember or snapshot what objects they are using under those names,
but that would still allow for much more customization I would think.

This wouldn't be a case where abuse would come in, I don't think, as only
the person(s) using the localpath would be affected visually.

If someone wanted a huge castle object with lots of polygons and intense
graphics, then only they would see that and be forced to deal with the lag.
:)

What does everyone think about this idea?

I have also decided to post this idea into my forums:
http://www.bastillion.net/forum/index.php?topic=71.0

Bastillion, Curator for The Bastion - A Gallery of Talented Builders
aw 1206n 7750w
http://www.bastillion.net
http://forum.bastillion.net

1  |  
Awportals.com is a privately held community resource website dedicated to Active Worlds.
Copyright (c) Mark Randall 2006 - 2024. All Rights Reserved.
Awportals.com   ·   ProLibraries Live   ·   Twitter   ·   LinkedIn