1  |   Order by index

Jun 13, 2002, 4:15am

For quite a while now I, and I am sure many others have tolerated the
Add/Delete combination of events when a user moves an object but its always
very inhibiting, needing to implement a separate queue inside the bot and
peek at the following events - but its still esentially a guess. Something
that would be infinitely more useful when dealing with building activities
would either be for the object number, X and Z coordinates of the previous
object (zeros if not applicable) to be included in the delete event or,
preferably, a new AW_EVENT_OBJECT_CHANGE event with the merged attributes of
the current add and delete event (using the existing AW_OBJECT_OLD_NUMBER,
AW_OBJECT_OLD_X and AW_OBJECT_OLD_Z attributes).

Ideally, I'd like to take that thought a stage further, where ALL of the
attributes of the deleted object (both in the delete event and any potential
change event) are supplied. When you're dealing with a large world,
pre-surveying is not feasible and with no prior knowledge of the object,
reversing a delete is impossible.

Being able to cause an object change but not detect one can be very
frustrating.

Grims

Jun 15, 2002, 10:01pm

lol yeah this would help i tried making a bot that replaced objects when you
tried deleting tourist property but it would take the attributes of the
object that had last been BUILT and not deleted!
[View Quote]

1  |   Order by index