Post by Swampfox on Apr 13, 2021 14:50:16 GMT
When Vivendi/Sierra/Dynamix spent the $7mm creating RedBaron3D, a few dollars was spent on designing algorithms. Some were made to make the Campaign the popular, many say the best, WWI or other Singleplayer which is highly respected today. The potential of the Campaign mode today is extraordinary. But today the competition has advanced their product(s) in every way.
Another algorithm in RedBaron3D is associated with Multiplayer, which contains some intentional functions designed to prevent cheating. Previously discussed is the 50% Rule on bombing. While it is a consistently reproducible effect based upon pilot decisions to bomb, then re-life without exiting to the "gold room", other things pilots can do can also trigger the target hardening effect. Everything could be fixed with one change in the code...simply turn off the end function into which all actions lead.
With that being said, the frequency of target hardening has been low for years with this community because of strictly exiting the arena to the Gold Room. However, as the number of total people flying in the server has increased, some consistent participants and some who come sometimes, it is likely that at least one or more "visitors" may not be as fastidious as the regulars. Who knows? Probably the scoring mechanism which starts with the DOS data output, which feeds into several community designed data management (keeping in mind that when a regular 8-8 targets layout is used, the game internally "scores" in order to declare a winner once the first 8 destroyed targets is reached) programs/apps like Chevelle's first of its kind, then Klay's, and at least one other take the DOS output data of in-game events, calculates scores based upon serverOp/community choices for plane kills and targets destroyed. The thing is...some actions like shooting your own target can also trigger a hardening and that can happen quite unintentionally as you are shooting the enemy as they bomb your drome, or any other target.
So, when the D5 drome apparently hardened last week, there is no way to know what caused it. An upgraded server program could, as mentioned above, eliminate all of that in one change and trying to analyze data which could tell who, what, when the hardening was caused would be a pointless effort.
The bottom line...and it is not perfect, is to go out of our way to communicate as best we can, when we can, to new or occasional pilots the importance of exiting upon death as most of us have practiced for decades. That is something we know can reduce the nasty target hardening event.
Swamp
Another algorithm in RedBaron3D is associated with Multiplayer, which contains some intentional functions designed to prevent cheating. Previously discussed is the 50% Rule on bombing. While it is a consistently reproducible effect based upon pilot decisions to bomb, then re-life without exiting to the "gold room", other things pilots can do can also trigger the target hardening effect. Everything could be fixed with one change in the code...simply turn off the end function into which all actions lead.
With that being said, the frequency of target hardening has been low for years with this community because of strictly exiting the arena to the Gold Room. However, as the number of total people flying in the server has increased, some consistent participants and some who come sometimes, it is likely that at least one or more "visitors" may not be as fastidious as the regulars. Who knows? Probably the scoring mechanism which starts with the DOS data output, which feeds into several community designed data management (keeping in mind that when a regular 8-8 targets layout is used, the game internally "scores" in order to declare a winner once the first 8 destroyed targets is reached) programs/apps like Chevelle's first of its kind, then Klay's, and at least one other take the DOS output data of in-game events, calculates scores based upon serverOp/community choices for plane kills and targets destroyed. The thing is...some actions like shooting your own target can also trigger a hardening and that can happen quite unintentionally as you are shooting the enemy as they bomb your drome, or any other target.
So, when the D5 drome apparently hardened last week, there is no way to know what caused it. An upgraded server program could, as mentioned above, eliminate all of that in one change and trying to analyze data which could tell who, what, when the hardening was caused would be a pointless effort.
The bottom line...and it is not perfect, is to go out of our way to communicate as best we can, when we can, to new or occasional pilots the importance of exiting upon death as most of us have practiced for decades. That is something we know can reduce the nasty target hardening event.
Swamp
