Dropped object problem?
I haven't heard of any problems related to dropped objects, but I found this interesting:
Code:
// Loading object from client dropping item on ground |
We have these all over the place, this is because we decided long ago to use the x,y format where live uses y,x
I thought the same thing when I initially say x being set to y (i was looking at mob position update packets) If dropped objects are appearing in the right place, then this is a non issue. |
Here it is again in client_process.cpp:
Code:
zp->zpe[count].x = data->target_y; Am I working under a wrong understanding? |
I think thats a better way too, but alas, not done...
I think its just mixed/matched because so many hands have been in there, so no one has gone in and applied a good consistant solution.. |
Not to mention the define INVERSEXY.. I don't think the code will work right at all without it. We should decide on how we want it done, document it clearly and just run with it. A lot of code to mess with either way though.
|
Actually, i searched through the code for that define, if i remember correctly its only used once in world (maybe not at all anymore)
|
yea but how many places is x assigned to y and vice versa? without a nice comment saying "leave it the F*** alone" :P
|
All times are GMT -4. The time now is 08:45 AM. |
Powered by vBulletin®, Copyright ©2000 - 2025, Jelsoft Enterprises Ltd.