|
dthknight // User Search
dthknight // User Search
Aug 8, 1999, 3:36pm
you can change the "Building Inspector: Please try building somewhere else
because this area is full" into "ERROR: Area full" though :) you rename the
BI in the AWM file (make a copy of the default.awm first though!) to
'ERROR', and then change the area full message to 'Area full'. And presto,
no more BI - at least not as we know him... area full and encroachment still
exist :)
[View Quote]Andras Sarkozy <andras at storage.co.hu> wrote in message
news:37AC8896.D370F923 at storage.co.hu...
> Another correction:
> You can't DISABLE the BI. You can only change the messages you got.
> Andras
>
>
> Sado Alanet wrote:
>
could change them and disable the BI from giving you messages.
track of encroachment, etc.
desired you could change the data files for the AW browser so that it just
said "ERROR 432: Encroachment."
you have ED or caretaker rights, but you can do more than a plain user. It
never "black-triangles" things.
or find the "non-registered" objects.
exceed it (again on the world server side).
an object but nothing else special. <you can't build on someones property if
you have the registry installed>
Then it just
|
Aug 9, 1999, 12:41am
FYI: You can't disable messages... you can make them look like this:
' : '
but that colon won't disappear... and to do that you need to use a special
character in the message file (just leaving the entries blank crashes AW, I
think... I remember Eep tried it once just with blank spaces)
[View Quote]Sado Alanet <s_alanet at NOSPAM.hotmail.com> wrote in message
news:37ADBE61.6C446703 at NOSPAM.hotmail.com...
> Disable = No messages.
>
> The world server is still gonna validate, and it's still gonna prevent you
from doing illegal building, but the BI will be out of the picture. The BI
is nothing more than a nice way for
> the world server to say "you can't do this".
>
> Sado
>
> Andras Sarkozy wrote:
>
you could change them and disable the BI from giving you messages.
keeps track of encroachment, etc.
so desired you could change the data files for the AW browser so that it
just said "ERROR 432: Encroachment."
if you have ED or caretaker rights, but you can do more than a plain user.
It never "black-triangles" things.
enroachment or find the "non-registered" objects.
exceed it (again on the world server side).
of an object but nothing else special. <you can't build on someones property
if you have the registry installed>
|
Oct 19, 2000, 3:31pm
I would have imagined that a single object refresh would just require
the browser to ask the web server for a re-download, and then simply
re-load the scene (which doesn't involve downloading) to show the new
object (assuming it is different, which could easily be checked using a
file comparison.)
[View Quote]goober king wrote:
>
> Interesting... a man who has dealt with COF in the past and knows how
> they feel about their customers is trying to start a petition... can
> anyone say "futility"?
>
> Still, I agree that having a 3.0 viewer would kick ass, but I'm not so
> sure about the single object refresh idea. It may be too complex to
> code. (not that I know what goes into such coding) Would the world
> server have to scan for that specific object and then refresh it? Might
> be a bit of a resource hog... Perhaps a "Refresh World" or "Refresh
> Scene" option would be better, where you just go up to a menu, pick
> "Refresh World", and all the objects in your view will re-download. This
> would be a user option as well, since there have been quite a few times
> where I've been in someone else's world and had to re-download the world
> cache just to see a different object...
> --
> Goober King
> The pessimist that just doesn't go away...
> rar1 at acsu.buffalo.edu
|
|