hi, i have a little problem with a new contaier...
i have create a new image of a recipient and with mulpatcher i hav put it in the first free gump slot (27).
so i have set in tiledata the flag "container" and i have saved.
in itemdesc i have create the container.
When i double click in the object, the gump appear and the object entred on the container but only in a specific rectangle.
If i change the maxX minX maxY minY, the position of the object is the same.
I think the problem is in the mul file but i don't know how I must do (i'm not a graphic designer).
i have see an old post in this forum with the same question but there isn't any solution
there is any function to manage it?
Help me please!!
thank you very much
Custom Container
Moderator: POL Developer
-
- Distro Developer
- Posts: 2825
- Joined: Thu Feb 02, 2006 1:41 pm
- Location: San Antonio, Texas
- Contact:
Re: Custom Container
Is there anyway you can post a screenshot?
That might help to give us a visual of what's happening.
That might help to give us a visual of what's happening.
Re: Custom Container
There is problem with custom container area. You can raise MinX, MaxX, MinY, MaxY, but in fact raising stop on value about 100x100.
To this value is everything ok. But then the item droped in container fall on direction 100x100. This problem came with new POL 97 and ML client. I think that this is step backward. But I dont know if it is problem of POL or ML client.
To this value is everything ok. But then the item droped in container fall on direction 100x100. This problem came with new POL 97 and ML client. I think that this is step backward. But I dont know if it is problem of POL or ML client.
Re: Custom Container
Any progress in this?
Re: Custom Container
I think this is only client related, i recently had the same problem. The 2d client has an intern table of the gump bounds. If it has to display a custom gump it somehow scales it. If you hook the 0x08 Drop item packet you will see that the client sends wrong coords. There is no way to tell the client via packets what the real min/max/xy values are...so the server does everything properly...