User:Qaisjp/sandbox-forks - Revision history

Qaisjp: redirect to forks

2020-02-02T18:53:35Z

redirect to forks

← Older revision		Revision as of 18:53, 2 February 2020
Line 1:		Line 1:
	~~__NOTOC__ {{Note\|Information on this page does not apply to the official builds of MTA.}}~~		#REDIRECT [[Forks]]

	~~Multi Theft Auto is open-source software, freely available on [https://github.com/multitheftauto/mtasa-blue GitHub multitheftauto/mtasa-blue].~~
	~~Anyone is free to fork the project as long as they abide by the terms of our license, The GNU General Public License v3.~~

	You can find explanations of the GNU GPL v3 here: [https://choosealicense.com/licenses/gpl-3.0/ choosealicense.com] and [https://tldrlegal.com/license/gnu-general-public-license-v3-(gpl-3) tldrlegal.com]. Our [https://github.com/multitheftauto/mtasa-blue/blob/master/LICENSE license] takes precedence, but this generally means that you must:

	* state significant changes made to the software
	* disclose the source code
	* share your code under the same license
	* include the original copyright notice

	If you are working on a fork, we ask that you include a link to your homepage and where we can find the source code. This allows us to keep up to date on projects and even introduce improvements to the vast majority of MTA players. Adding your Discord name is not compulsory, but if you ask for development help on our GitHub, forum or Discord, it helps us know what project you are from and that you are abiding by the license.

	~~== List of forked projects ==~~

	* '''example''': [https://example.com Example project] (source on [https://github.com/multitheftauto/mtasa-blue GitHub])
	** Maintainers: @someuser#~~1234,~~ [~~https://discordapp.com/users/83386293446246400 @anotheruser#5678],~~ [~~https://github.com/ghost @ghost], [https://forum.mtasa.com/profile/39572-test/ @test]~~
	* ...

	== Forks ~~and anti-cheat==~~

	~~(from https://wiki.multitheftauto.com/wiki/Anti-cheat_support_for_custom_builds)~~

	~~Custom MTA builds and forked projects will face some challenges relating to anti-cheat (AC). This is due to custom builds performing in ways that the anti-cheat module does not expect.~~
	<br />The anti-cheat and netcode components (netc.dll, net.dll, FairplayKD.sys) are, unlike MTA itself, closed-source, and therefore without informing yourself it would be hard to overcome the challenges.

	AC is generally unsupported for forked projects and may be dropped entirely in the future. This means that you generally ''cannot'' rely on the MTA anti-cheat for your fork. '''We strongly advise that you write and implement your own AC.'''

	~~If you cannot build your own AC, here are steps you can follow to get the most out of our (unsupported) AC:~~

	* Always use the version of our net modules (e.g [https://mirror.mtasa.com/bdata/netc.dll netc.dll] ~~and [https://mirror.mtasa.com/bdata/net.dll net.dll~~]~~) that matches our commit on master that your fork is based on~~
	** To be specific, you can use the latest module that is bitstream version compatible
	** You can fetch these modules by running https://github.com/multitheftauto/mtasa-blue/blob/master/win-build.bat
	* Never block MTA traffic (client or server) in your project

	~~=== AC features missing in custom builds ===~~
	* No detection of changes to gta_sa code section
	* No detection of changes to certain gta_sa variables
	* SetElementData not protected against external changes
	* No detection against various Lua injection methods
	* Much fewer AC heuristics and protection of internals
	* Continuous updates for all patched methods and vulnerabilities to write cheats based on aren't guaranteed (occasionally, they are cherry-picked; one of the reasons why updating netc.dll to the latest offered version is beneficial)
	* MTA modules aren't checked for modifications or remote hooking/memory writing
	* and much more

	Generally, most of what will work are some signature-based detections. No heuristics, patched methods, and patched vulnerabilities. Signature-based detections are the weakest kind, and the mainstream anti-cheat tackles the actual problem rather than being signature-based.

Dutchman101 at 01:45, 17 January 2020

2020-01-17T01:45:12Z

← Older revision		Revision as of 01:45, 17 January 2020
Line 24:		Line 24:

	Custom MTA builds and forked projects will face some challenges relating to anti-cheat (AC). This is due to custom builds performing in ways that the anti-cheat module does not expect.		Custom MTA builds and forked projects will face some challenges relating to anti-cheat (AC). This is due to custom builds performing in ways that the anti-cheat module does not expect.
	The anti-cheat and netcode components (netc.dll, net.dll, FairplayKD.sys) are, unlike MTA itself, closed-source, and therefore without informing yourself it would be hard to overcome the challenges.		<br />The anti-cheat and netcode components (netc.dll, net.dll, FairplayKD.sys) are, unlike MTA itself, closed-source, and therefore without informing yourself it would be hard to overcome the challenges.

	AC is generally unsupported for forked projects and may be dropped entirely in the future. This means that you generally ''cannot'' rely on the MTA anti-cheat for your fork. '''We strongly advise that you write and implement your own AC.'''		AC is generally unsupported for forked projects and may be dropped entirely in the future. This means that you generally ''cannot'' rely on the MTA anti-cheat for your fork. '''We strongly advise that you write and implement your own AC.'''

Dutchman101 at 01:44, 17 January 2020

2020-01-17T01:44:36Z

← Older revision		Revision as of 01:44, 17 January 2020
Line 24:		Line 24:

	Custom MTA builds and forked projects will face some challenges relating to anti-cheat (AC). This is due to custom builds performing in ways that the anti-cheat module does not expect.		Custom MTA builds and forked projects will face some challenges relating to anti-cheat (AC). This is due to custom builds performing in ways that the anti-cheat module does not expect.
			The anti-cheat and netcode components (netc.dll, net.dll, FairplayKD.sys) are, unlike MTA itself, closed-source, and therefore without informing yourself it would be hard to overcome the challenges.

	AC is generally unsupported for forked projects and may be dropped entirely in the future. This means that you generally ''cannot'' rely on the MTA anti-cheat for your fork. '''We strongly advise that you write and implement your own AC.'''		AC is generally unsupported for forked projects and may be dropped entirely in the future. This means that you generally ''cannot'' rely on the MTA anti-cheat for your fork. '''We strongly advise that you write and implement your own AC.'''

Dutchman101: t

2020-01-17T01:38:38Z

← Older revision		Revision as of 01:38, 17 January 2020
Line 40:		Line 40:
	* No detection against various Lua injection methods		* No detection against various Lua injection methods
	* Much fewer AC heuristics and protection of internals		* Much fewer AC heuristics and protection of internals
	* Continuous updates for all patched methods to write cheats based on ~~(vulnerabilities)~~ aren't guaranteed (~~this is~~ one of the reasons why updating netc.dll to the latest offered version is beneficial)		* Continuous updates for all patched methods and vulnerabilities to write cheats based on aren't guaranteed (occasionally, they are cherry-picked; one of the reasons why updating netc.dll to the latest offered version is beneficial)
	* MTA modules aren't checked for modifications or remote hooking/memory writing		* MTA modules aren't checked for modifications or remote hooking/memory writing
	* and much more		* and much more

	Generally, most of what will work are some signature-based detections. No heuristics, patched methods, and patched vulnerabilities. Signature-based detections ~~of known cheats~~ are the weakest ~~kinds of cheats~~, and the mainstream anti-cheat tackles the actual problem rather than being signature-based.		Generally, most of what will work are some signature-based detections. No heuristics, patched methods, and patched vulnerabilities. Signature-based detections are the weakest kind, and the mainstream anti-cheat tackles the actual problem rather than being signature-based.

Qaisjp: test forum link

2020-01-16T22:08:15Z

test forum link

← Older revision		Revision as of 22:08, 16 January 2020
Line 16:		Line 16:

	* '''example''': [https://example.com Example project] (source on [https://github.com/multitheftauto/mtasa-blue GitHub])		* '''example''': [https://example.com Example project] (source on [https://github.com/multitheftauto/mtasa-blue GitHub])
	** Maintainers: @someuser#1234, [https://discordapp.com/users/83386293446246400 @anotheruser#5678], [https://github.com/ghost @ghost]		** Maintainers: @someuser#1234, [https://discordapp.com/users/83386293446246400 @anotheruser#5678], [https://github.com/ghost @ghost], [https://forum.mtasa.com/profile/39572-test/ @test]
	* ...		* ...

Qaisjp: add forum

2020-01-16T22:07:30Z

add forum

← Older revision		Revision as of 22:07, 16 January 2020
Line 11:		Line 11:
	* include the original copyright notice		* include the original copyright notice

	If you are working on a fork, we ask that you include a link to your homepage and where we can find the source code. This allows us to keep up to date on projects and even introduce improvements to the vast majority of MTA players. Adding your Discord name is not compulsory, but if you ask for development help on our GitHub or Discord, it helps us know what project you are from and that you are abiding by the license.		If you are working on a fork, we ask that you include a link to your homepage and where we can find the source code. This allows us to keep up to date on projects and even introduce improvements to the vast majority of MTA players. Adding your Discord name is not compulsory, but if you ask for development help on our GitHub, forum or Discord, it helps us know what project you are from and that you are abiding by the license.

	== List of forked projects ==		== List of forked projects ==

Qaisjp: add link

2020-01-16T22:06:11Z

add link

← Older revision		Revision as of 22:06, 16 January 2020
Line 16:		Line 16:

	* '''example''': [https://example.com Example project] (source on [https://github.com/multitheftauto/mtasa-blue GitHub])		* '''example''': [https://example.com Example project] (source on [https://github.com/multitheftauto/mtasa-blue GitHub])
	** Maintainers: @someuser#1234, @anotheruser#5678, [https://github.com/ghost @ghost]		** Maintainers: @someuser#1234, [https://discordapp.com/users/83386293446246400 @anotheruser#5678], [https://github.com/ghost @ghost]
	* ...		* ...

Qaisjp: add license link

2020-01-16T21:50:09Z

add license link

← Older revision		Revision as of 21:50, 16 January 2020
Line 4:		Line 4:
	Anyone is free to fork the project as long as they abide by the terms of our license, The GNU General Public License v3.		Anyone is free to fork the project as long as they abide by the terms of our license, The GNU General Public License v3.

	You can find explanations of the GNU GPL v3 here: [https://choosealicense.com/licenses/gpl-3.0/ choosealicense.com] and [https://tldrlegal.com/license/gnu-general-public-license-v3-(gpl-3) tldrlegal.com]. Our license takes precedence, but this generally means that you must:		You can find explanations of the GNU GPL v3 here: [https://choosealicense.com/licenses/gpl-3.0/ choosealicense.com] and [https://tldrlegal.com/license/gnu-general-public-license-v3-(gpl-3) tldrlegal.com]. Our [https://github.com/multitheftauto/mtasa-blue/blob/master/LICENSE license] takes precedence, but this generally means that you must:

	* state significant changes made to the software		* state significant changes made to the software

Qaisjp: add fork info

2020-01-16T21:46:44Z

add fork info

← Older revision		Revision as of 21:46, 16 January 2020
Line 1:		Line 1:
	~~'''This page is intended for maintainers of custom MTA builds or forked projects based on the MTA source code.~~ Information on this page does not apply to the official builds of MTA.~~'''~~		__NOTOC__ {{Note\|Information on this page does not apply to the official builds of MTA.}}

	Custom MTA builds and forked projects will face some challenges relating to anti-cheat (AC). This is due to custom builds performing in ways that the anti-cheat does not expect.		Multi Theft Auto is open-source software, freely available on [https://github.com/multitheftauto/mtasa-blue GitHub multitheftauto/mtasa-blue].
			Anyone is free to fork the project as long as they abide by the terms of our license, The GNU General Public License v3.

			You can find explanations of the GNU GPL v3 here: [https://choosealicense.com/licenses/gpl-3.0/ choosealicense.com] and [https://tldrlegal.com/license/gnu-general-public-license-v3-(gpl-3) tldrlegal.com]. Our license takes precedence, but this generally means that you must:

			* state significant changes made to the software
			* disclose the source code
			* share your code under the same license
			* include the original copyright notice

			If you are working on a fork, we ask that you include a link to your homepage and where we can find the source code. This allows us to keep up to date on projects and even introduce improvements to the vast majority of MTA players. Adding your Discord name is not compulsory, but if you ask for development help on our GitHub or Discord, it helps us know what project you are from and that you are abiding by the license.

			== List of forked projects ==

			* '''example''': [https://example.com Example project] (source on [https://github.com/multitheftauto/mtasa-blue GitHub])
			** Maintainers: @someuser#1234, @anotheruser#5678, [https://github.com/ghost @ghost]
			* ...

			== Forks and anti-cheat==

			(from https://wiki.multitheftauto.com/wiki/Anti-cheat_support_for_custom_builds)

			Custom MTA builds and forked projects will face some challenges relating to anti-cheat (AC). This is due to custom builds performing in ways that the anti-cheat module does not expect.

	AC is generally unsupported for forked projects and may be dropped entirely in the future. This means that you generally ''cannot'' rely on the MTA anti-cheat for your fork. '''We strongly advise that you write and implement your own AC.'''		AC is generally unsupported for forked projects and may be dropped entirely in the future. This means that you generally ''cannot'' rely on the MTA anti-cheat for your fork. '''We strongly advise that you write and implement your own AC.'''

	If you cannot build your own AC, here are steps you can follow to get the most out of our unsupported AC:		If you cannot build your own AC, here are steps you can follow to get the most out of our (unsupported) AC:

	* Always use the version of our net modules (e.g [https://mirror.mtasa.com/bdata/netc.dll netc.dll] and [https://mirror.mtasa.com/bdata/net.dll net.dll]) that matches our commit on master that your fork is based on		* Always use the version of our net modules (e.g [https://mirror.mtasa.com/bdata/netc.dll netc.dll] and [https://mirror.mtasa.com/bdata/net.dll net.dll]) that matches our commit on master that your fork is based on
Line 12:		Line 34:
	* Never block MTA traffic (client or server) in your project		* Never block MTA traffic (client or server) in your project

	== AC features missing in custom builds ==		=== AC features missing in custom builds ===
	* No detection of changes to gta_sa code section		* No detection of changes to gta_sa code section
	* No detection of changes to certain gta_sa variables		* No detection of changes to certain gta_sa variables

Qaisjp: Qaisjp moved page User:Qaisjp/sandbox-ac-support to User:Qaisjp/sandbox-forks without leaving a redirect

2020-01-16T21:31:01Z

Qaisjp moved page User:Qaisjp/sandbox-ac-support to User:Qaisjp/sandbox-forks without leaving a redirect

← Older revision

Revision as of 21:31, 16 January 2020