Quote:
Originally Posted by ntKid
Wallhack and chams for mats, these are just visual effects with no use at all, has nothing to do with a harvesting bot
|
I was asked if it was possible to currently detect loaded textures and manipulate them by chance, I was merely showing that it is possible to get the currently loaded texture, the coordinates and the actual filename to what the indicated resource may belong to.
But I guess you couldnt see that since the picture was being deleted.
Quote:
Originally Posted by ntKid
unless you have a worldtoscreen or a pixel check, either way that will suck because the mat needs to be on player current field of vision for you to go pick.
|
You're wrong, on both ends. A WTS Calculation is something you can find like sand on a beach, however it is not required to accomplish something like that and I dont know why you even wrote it up. But what you are looking for are to hook the Vertex and Transform functions that will give the World Coordinates of a Texture or a Mesh. Also, the Model Recognition is very important, it is required to define what location you will receive, if not you would end up with a bunch of thousand coordinates. I don't really know why you call that useless. You can also solve this by calculating from the entity base in the memory.
Anyway, another problem you're wrong at: You don't need to be seeing the material to actually waypoint there, since you got the coordinates from your function (Even a simple pixel search can calculate the world coordinates btw!). If you wan't to go the hard way you have to make your bot understand when it will hit an obstruction, and then automatically build temporary waypoints around it in few defined gaps, if the second attempt fails your bot should use a different scheme of getting arround. This is not very hard and can be seen in Zero's Bot.
The easy way would be simply modificating the game client, the Server doesn't control if the client is within a collision zone or not, but theres a fixed amount of what you can go in the Z,Y,X direction. This however, would be a 3rd party solution which you don't seem to like either because you already showed off something like this.