There's a new update for mta (1.3.5) so in order to be able to use onClientVehicleDamage, the client version must be min. 1.3.5; For this reason, I changed the minclientversion parameter in mtaserver.conf and set it to the lattest version and build.
1.3.5-9.06121.0
But, a couple of people and myself experimented a 'wierd' situation when the server asked to update MTA, and we clicked OK, it said: No update avalable/n visit: mtasa.com
Question
'LinKin
Hello,
There's a new update for mta (1.3.5) so in order to be able to use onClientVehicleDamage, the client version must be min. 1.3.5; For this reason, I changed the minclientversion parameter in mtaserver.conf and set it to the lattest version and build.
1.3.5-9.06121.0
But, a couple of people and myself experimented a 'wierd' situation when the server asked to update MTA, and we clicked OK, it said: No update avalable/n visit: mtasa.com
I had to download the .exe and reinstall my mta.
Link to comment
2 answers to this question
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now