sbx320

In den Optionen unter Video -> Full Screen Minimize den Haken setzen.

I had some troubles when I converted ides to MTA objects a few months back. Going to look into that again when I get home. Should totally be solveable.

The rotation you're searching for should be (0|-180|0). These two functions might help for automatic processing of .ide's: (Keep in mind that math.toeuler takes w as first parameter, while in .ide's W is the last rotation parameter) -- Return order is w, x, y, z function math.toquaternion(x, y, z) x = math.rad(x)/2 y = math.rad(y)/2 z = math.rad(z)/2 return math.cos(x) * math.cos(y) * math.cos(z) - math.sin(x) * math.sin(y) * math.sin(z), math.sin(x) * math.sin(y) * math.cos(z) + math.cos(x) * math.cos(y) * math.sin(z), math.sin(x) * math.cos(y) * math.cos(z) + math.cos(x) * math.sin(y) * math.sin(z), math.cos(x) * math.sin(y) * math.cos(z) - math.sin(x) * math.cos(y) * math.sin(z) end function math.toeuler(w, x, y, z) return math.deg(math.atan2(2*(y*w-x*z), 1-2*y^2-2*z^2)), math.deg(math.asin(2*(x*y+z*w))), math.deg(math.atan2(2*x*w-2*y*z,1-2*x^2-2*z^2)) end

There are always new cheats being developed. The Anticheat is constantly updated, but you can never be aware of all cheats out there at all times. You can't ever trust a client. The security advantage of a custom system based upon event triggers is that by default you do not have an insecure system. With ElementDatas you need to take action to prevent cheaters. With custom event triggers you might as well chose to not allow clients to change certain data by simply not implementing the corresponding events serverside.

You're correct on what you stated above. onClientElementDataChange won't send the old value, since the client already knows it. I'd suggest you to use a custom system based upon triggerClientEvent, since element datas have a few issues: They're synced to everyone Whenever you change an Elementdata on the server/client the information will be synced to any connected client. This is often not necessary, but simply a waste of bandwidth. Why would a remote player be required to know the exact amount of fuel in a vehicle far away? That information is only useful for the driver of the vehicle, so you'd waste a ton of bandwidth which could be used by MTA for better synchronization. Anyone can modify them Without some additional security scripts (which is easily possible, but often overlooked) any client can modify Elementdatas of any element. This allows cheaters with modified clients to cheat themselves various things like money or even admin rights.

This was already implemented in 1.4 some time ago. See http://sbx320.net/mta/14preview_ban.png for a small preview.

Ist nicht möglich und wird vorraussichtlich auch nicht eingebaut.

(To clear things up: I'm also one of the scripters behind this project) Modifying weapons would of cause be an interesting option. But, as we do not want to "steal" from others, we would either need the sounds/mods creators permission or create our own. So we'd need someone who is able to create models/sounds, as - for example - I can't do that in a proper quality. This is mainly the point where we need the community's support. We might be good at scripting, but we're not good in terms of designing things.