[IllidanS4]

Quote:

Originally Posted by Kalcor 0.3.7 server owners report in if you see this. Are you happy with a 0.3.7 update (0.3.9) which just updates packet IDs and memory addresses?

0.3.7 sandbox server owner reporting in. Since cheating tools are not prohibited on my server, and I quite heavily rely on the usage of YSF, this kind of an update would just require me to do a lot of work with no gained advantage. Perhaps I would even stay at 0.3.7 if that amount of work were too big.

I would welcome an update if at least something got added. These things are currently what I request:

• Make "lights" in SetVehicleParamsEx work like "engine". 1 - permanently turned on, 0 - permanently turned off, -1 - depending on the environment (night, tunnels). Without having to use ManualVehicleEngineAndLights at all.
• Increasing the object count to 2000 like it is in DL. Custom models or not, mapping is still popular and 1000 is too little. Since the code is already in DL, shouldn't be such an issue.
• Make UsePlayerPedAnims per-player and changeable for anyone in the middle of the game.
• DisableRemoteVehicleCollisions on a per-vehicle basis, and working on unoccupied vehicles as well. DisableObjectCollision would also come in handy.
• An ability to revert the effect of a particular RemoveBuildingForPlayer (or all of them), and increasing the amount of these calls from 1000 (and without crashing the client). If the client reconnects, there should be a way of reverting these automatically, since when 501 buildings are removed and the client reconnects once, their game crashes.
• "materialindex" in SetObjectMaterial and SetObjectMaterialText increased from 15, as there are objects with more than 16 material surfaces.
  

Believe it or not, I would have a use for all of these, regardless of potential desyncs. Then and only then would be the work I will need to do updating YSF justified.

Quote:

Originally Posted by Kalcor You need GTA:SA modding experience to work on samp. That's a rare thing in 2019.

Only on the client. I believe there are other experts like you that perhaps could be found, and people can learn how these things work. Memory addresses, opcodes, and stuff, many people have experimented with those.

The server is a completely different thing. I have even argued that only open-sourcing the server would be nice, as there are some security issues, long-living bugs, and missing natives and features, that can be implemented without touching the client (that's why YSF is here in the first place).

There are still many competent and dedicated programmers left here. I have even contributed to SA-MP once if you remember (0.3d skins).

Quote:

Originally Posted by Kalcor I don't think there's enough interest in modeling to push DL out as the main branch. There have been no updates to the blender scripts, no tools developed.

I have seen enough interest in modeling before the introduction of DL and even after it. People were importing maps, creating fully featured skins; I have even seen a semi-working horse script. The lack of interest has been created not because people simply don't want these features, but by fracturing the community this way.

Speaking as the owner of a sandbox server, I would accept any player with 0.3.7 or 0.3.DL at the same time, and since I use virtual worlds, I can make DL-only virtual worlds for those players. Such a feature is not something you choose to have or not to have, it's a feature you should be able to use if the player accepts it.

Quote:

Originally Posted by Kalcor Now here's the fucked up thing that happens. The "game" layer I designed for MTA, and source code that R* gave them, get imported in to mod_so-beit, a popular hack tool for SA-MP. Do you know what that means? THE LARGEST USE OF THE SOURCE CODE R* GAVE TO MTA WAS TO HACK SA-MP! What started out as a small group of developers on MTA, who were fairly professional, became extremely dirty over time. The people wanting to take down SA-MP are not concerned about breaking the law in order to do so!

Given enough time, people would reverse-engineer this stuff anyway. Perhaps it would take them more time, but here in 2019 I don't think anything would be too different if this hadn't happened. I am not denying them taking part in this, but that is a thing of the past.

Quote:

Originally Posted by Kalcor It seems just as likely that any source code given out would be used to attack SA-MP, as it would to provide useful updates. The decision to release SA-MP's source code comes down to whether we're still in this hostile environment where people are attacking me and wanting to attack SA-MP, or whether we've moved beyond it. I would say it comes down to the size of the mod and the demand for hacking tools. Being closed source has allowed me to shuffle all the internal structures and obsolete many of the hacking tools with each release. Many of the "security" updates for SA-MP have just been me shuffling around data to throw off hacking tools.

I am sorry for partially contributing to the "hate" that had transpired, but I think myself and many other people have done things out of desperation seeing that SA-MP is not updated. Are we still in this environment? No, I don't think we are, just evident from the posts in this thread. Some people plead for updates, some understand you and your right to lose passion for development; of course there is the fair share of trolls, but comparing this to many occasions in the past, this is an honest discussion me and many other people wanted, driven by reason and not by emotions.

Recompiling the code just to change memory addresses does prevent cheats for a while, but you are a single person, while the hackers are many. Now there are server-side and even client-side anticheats, and even limited open-sourcing (or better API than the AMX plugin API) would be helpful to the developers of those and not much to the hackers (as they have already reversed engineered it all).