Modding:Open source - Revision history

imported>VulpesLucida: zh link

2024-12-16T13:31:27Z

zh link

← Older revision		Revision as of 13:31, 16 December 2024
Line 118:		Line 118:
	[[ru:Модификации:Open source]]		[[ru:Модификации:Open source]]
	[[tr:Modlama:Açık Kaynak]]		[[tr:Modlama:Açık Kaynak]]
			[[zh:模组:开源代码]]

imported>Peaw at 11:21, 17 July 2024

2024-07-17T11:21:05Z

← Older revision		Revision as of 11:21, 17 July 2024
Line 117:		Line 117:
	[[pt:Modificações:Open Source]]		[[pt:Modificações:Open Source]]
	[[ru:Модификации:Open source]]		[[ru:Модификации:Open source]]
			[[tr:Modlama:Açık Kaynak]]

imported>Atravita: /* If your code isn't on GitHub */

2023-08-15T01:00:10Z

If your code isn't on GitHub

← Older revision		Revision as of 01:00, 15 August 2023
Line 47:		Line 47:
	This looks like a lot of steps, but don't worry: it's pretty straightforward, and you only need to do it once. If you need help, come ask in [[Modding:Community#Discord\|#making-mods on the Stardew Valley Discord]]. :)		This looks like a lot of steps, but don't worry: it's pretty straightforward, and you only need to do it once. If you need help, come ask in [[Modding:Community#Discord\|#making-mods on the Stardew Valley Discord]]. :)

			====Via VisualStudio====

			Visual Studio has a pretty good git integration, documented here: https://learn.microsoft.com/en-us/visualstudio/version-control/git-create-repository?view=vs-2022

			====Via SourceTree====
	<dl>		<dl>
	<dt>Create a Git repository</dt>		<dt>Create a Git repository</dt>

imported>Margotbean: /* If your code isn't on GitHub */ attempt to add sourcetree steps from talk page

2023-08-14T15:48:32Z

If your code isn't on GitHub: attempt to add sourcetree steps from talk page

@@ Line 66: / Line 66: @@
 <li>On the repository page that appears, click the green "Clone or download" button and copy the URL:<br />[[File:Modding - copy GitHub repo URL.png]]</li>
 <li>In SourceTree, click ''File > Clone'' and paste the URL. Choose a destination path that's easy to access (like <samp>C:\source\StardewMods</samp>), and click 'Clone'.</li>
 </ol>

imported>Margotbean at 02:06, 13 July 2023

2023-07-13T02:06:04Z

← Older revision		Revision as of 02:06, 13 July 2023
Line 99:		Line 99:

	[[es:Modding:Código abierto]]		[[es:Modding:Código abierto]]
			[[pt:Modificações:Open Source]]
	[[ru:Модификации:Open source]]		[[ru:Модификации:Open source]]
	~~[[pt:Modificações:Open source]]~~

imported>DELET at 01:41, 13 July 2023

2023-07-13T01:41:03Z

← Older revision		Revision as of 01:41, 13 July 2023
Line 100:		Line 100:
	[[es:Modding:Código abierto]]		[[es:Modding:Código abierto]]
	[[ru:Модификации:Open source]]		[[ru:Модификации:Open source]]
			[[pt:Modificações:Open source]]

imported>Pathoschild: /* Common questions */ move Git repo question to bottom

2023-06-12T15:48:53Z

Common questions: move Git repo question to bottom

← Older revision		Revision as of 15:48, 12 June 2023
Line 27:		Line 27:
	; What if I don't like a proposed change?		; What if I don't like a proposed change?
	: You still have full control of your original code and mod pages; nobody can change those without your approval! You're free to reject a change someone proposes to your mod.		: You still have full control of your original code and mod pages; nobody can change those without your approval! You're free to reject a change someone proposes to your mod.

	~~; What is a Git repository?~~
	: Git is software that helps track changes to your code, and a repository is a folder containing your mod files with Git tracking. You can look up Git tutorials if you want to know more, but don't worry: you don't need to know how it works to use it!

	; Does this apply for content packs?		; Does this apply for content packs?
Line 39:		Line 36:
	; I already released the mod without a license. Can I add a license now?		; I already released the mod without a license. Can I add a license now?
	: Yes. If you created the entire mod yourself, you can add or change the license anytime. If others contributed to the mod (including code, translations, or images), you'll need to either get permission from each contributor to relicense their contributions, or strip their changes out of the mod.		: Yes. If you created the entire mod yourself, you can add or change the license anytime. If others contributed to the mod (including code, translations, or images), you'll need to either get permission from each contributor to relicense their contributions, or strip their changes out of the mod.

			; What is a Git repository?
			: Git is software that helps track changes to your code, and a repository is a folder containing your mod files with Git tracking. You can look up Git tutorials if you want to know more, but don't worry: you don't need to know how it works to use it!

	==Make your code open-source==		==Make your code open-source==

imported>Pathoschild: /* Common questions */ + retroactive licensing

2022-08-10T16:13:14Z

Common questions: + retroactive licensing

← Older revision		Revision as of 16:13, 10 August 2022
Line 36:		Line 36:
	; Can I prevent commercial use?		; Can I prevent commercial use?
	: A non-commercial license prevents others from profiting from or reselling the content. It's certainly better than no license at all, but it's ''not'' open-source. This can have unintended side-effects like preventing streamers from showing your mods because their videos are monetized. Avoiding non-commercial licenses is strongly recommended.		: A non-commercial license prevents others from profiting from or reselling the content. It's certainly better than no license at all, but it's ''not'' open-source. This can have unintended side-effects like preventing streamers from showing your mods because their videos are monetized. Avoiding non-commercial licenses is strongly recommended.

			; I already released the mod without a license. Can I add a license now?
			: Yes. If you created the entire mod yourself, you can add or change the license anytime. If others contributed to the mod (including code, translations, or images), you'll need to either get permission from each contributor to relicense their contributions, or strip their changes out of the mod.

	==Make your code open-source==		==Make your code open-source==

imported>Pathoschild: /* Why is open source important? */ + importance for contributions

2022-08-10T16:09:14Z

Why is open source important?: + importance for contributions

← Older revision		Revision as of 16:09, 10 August 2022
Line 4:		Line 4:

	==Why is open source important?==		==Why is open source important?==
	Open source is important for the long-term health of the modding community, and helps make the player experience smoother~~. Depending on the open-source license you choose, others can..~~.		Open source is important for the long-term health of the modding community, and helps make the player experience smoother.

	* see your code;		; How it benefits others
	* make changes to a copy of the ~~code;~~		: Depending on the open-source license you choose, others can...
	* send you ~~proposed updates, changes~~, ~~and fixes;~~
	* prepare unofficial updates;
	* better help users with support questions by looking at the code.

	The effect can be significant: only 1% of open-source mods broke when SMAPI 3.0 released, compared to '''51%''' of closed-source mods (and that doesn't count closed-source mods that were never updated for ~~recent~~ game releases).		:* see your code;
			:* make changes to a copy of the code;
			:* send you proposed updates, changes, and fixes;
			:* prepare unofficial updates;
			:* better help users with support questions by looking at the code.

			: The effect can be significant: only 1% of open-source mods broke when SMAPI 3.0 released, compared to '''51%''' of closed-source mods (and that doesn't count closed-source mods that were never updated for earlier game/SMAPI releases).

			; How it benefits you
			: Besides the above benefits, a license is very important if you'll accept contributions from others.

			: ''Without'' a license, contributors have a copyright for changes they make to your mod (like code, translation, or content changes). By contributing to your mod, they're implicitly giving you permission to use the content/changes in the way they're currently used. But since you no longer own the entire mod, you can't change how they're published (e.g. splitting the mod into smaller components, copying code into another mod, etc) without getting permission from each past contributor. And if some of those contributors can't be reached, you're out of luck unless you strip their contributions out of the mod entirely.

			: ''With'' a license, any contributions are automatically covered by the license too. That means you can do anything with the contributions that the license allows.

	==Common questions==		==Common questions==

imported>Pathoschild: /* Common questions */ + "Can I prevent commercial use?"

2022-06-12T19:29:29Z

Common questions: + "Can I prevent commercial use?"

← Older revision		Revision as of 19:29, 12 June 2022
Line 23:		Line 23:
	; Does this apply for content packs?		; Does this apply for content packs?
	: Yep! Content packs aren't compiled, but other modders can't legally make changes without a code license. Note that 'permissions' options on sites like Nexus are legally iffy (''e.g.,'' who has copyright on derivatives? Can derivatives be relicensed?), so it's a good idea to have a code license for content packs too. That also lets other modders contribute pull requests and updates. When this page says 'code', it means everything in your content pack including JSON files, images, maps, etc.		: Yep! Content packs aren't compiled, but other modders can't legally make changes without a code license. Note that 'permissions' options on sites like Nexus are legally iffy (''e.g.,'' who has copyright on derivatives? Can derivatives be relicensed?), so it's a good idea to have a code license for content packs too. That also lets other modders contribute pull requests and updates. When this page says 'code', it means everything in your content pack including JSON files, images, maps, etc.

			; Can I prevent commercial use?
			: A non-commercial license prevents others from profiting from or reselling the content. It's certainly better than no license at all, but it's ''not'' open-source. This can have unintended side-effects like preventing streamers from showing your mods because their videos are monetized. Avoiding non-commercial licenses is strongly recommended.

	==Make your code open-source==		==Make your code open-source==