Writing Submissions - Revision history

Jpmaggers at 12:33, 3 December 2022

2022-12-03T12:33:54Z

Jpmaggers at 12:33, 3 October 2022

2022-10-03T12:33:59Z

Jpmaggers at 12:31, 3 October 2022

2022-10-03T12:31:02Z

Jpmaggers at 12:29, 3 October 2022

2022-10-03T12:29:43Z

Jpmaggers at 12:29, 3 October 2022

2022-10-03T12:29:32Z

Jpmaggers at 12:29, 3 October 2022

2022-10-03T12:29:09Z

Jpmaggers at 12:28, 3 October 2022

2022-10-03T12:28:52Z

Jpmaggers at 12:27, 3 October 2022

2022-10-03T12:27:54Z

Jpmaggers at 12:27, 3 October 2022

2022-10-03T12:27:07Z

Jpmaggers at 12:21, 3 October 2022

2022-10-03T12:21:36Z

@@ Line 3: / Line 3: @@
 # '''I reserve the right to reject submissions''' - Whether due to inconsistencies with the world-building, issues of writing quality, problems with the legality of the content involved, or any other reason, I will reserve the right to reject writing submissions. As such, I also suggest if you have any ideas for a writing submission that you send me a quick message over on Discord to make sure it's something that will be allowed into the game.
 # '''I reserve the right to retain the content after submission without dispute''' - Working to fit writing into the game is a big task between the editing and coding process, as such once writing is submitted removing it would be a difficult process that I would like to avoid outside of extreme circumstances (such as plagiarised material). It is also worth noting that I do make a profit from my gave development, therefore if you're not comfortable with that then please do not submit writing to me.
 # '''All writing submissions will be fully credited''' - When people do work for me I always want them to be rewarded for that, and that includes crediting the work they've done. As such, all submitted scenes will feature a note on who submitted them. This submission name does not need to be your real name, it can be your username, or some other pseudonym if the writer would prefer that.
 # '''All characters featured within writing submissions should neither be copyrighted or a representation of a real person''' - This is a legal matter, but copyrighted characters or characters that represent real people are trouble, so I'll avoid submissions that include these. If the character is loosely 'based' on a real person, or is an author insert, then that would be okay, but generally I like to avoid any murky ground like this.
@@ Line 9: / Line 10: @@
 # '''The writing must have a 2nd person point of view''' - The game's writing style is a 2nd person point of view, as such writing submissions must match that or have a very good reason why they are not (such as writing submissions for C.U.M Box shows).
 # '''I am willing to do minor coding additions to submissions but not major ones''' - Inevitably, there will be times when it is necessary for me to do coding work to make writing submissions work. I do not expect the people offering writing submissions to have coding experience, or understand the Twine/Sugarcube engine/format. However, where coding is necessary it is preferable for the coding to be minor (such as linking the scene up, exp additions, minor existing item gains, description calls, etc.) rather than major ones (such as creation of new items, new in-game transformations, mini-games, complex variables to control NPC's, etc.). I'm happy to get a scene functional, but would turn down scenes that require that excessive coding/editing workload.
 == Basic Coding Syntax ==

@@ Line 9: / Line 9: @@
 # '''The writing must have a 2nd person point of view''' - The game's writing style is a 2nd person point of view, as such writing submissions must match that or have a very good reason why they are not (such as writing submissions for C.U.M Box shows).
 # '''I am willing to do minor coding additions to submissions but not major ones''' - Inevitably, there will be times when it is necessary for me to do coding work to make writing submissions work. I do not expect the people offering writing submissions to have coding experience, or understand the Twine/Sugarcube engine/format. However, where coding is necessary it is preferable for the coding to be minor (such as linking the scene up, exp additions, minor existing item gains, description calls, etc.) rather than major ones (such as creation of new items, new in-game transformations, mini-games, complex variables to control NPC's, etc.). I'm happy to get a scene functional, but would turn down scenes that require that excessive coding/editing workload.
 == Basic Coding Syntax ==

← Older revision		Revision as of 12:31, 3 October 2022
Line 17:		Line 17:
	== Specific Description Calls ==		== Specific Description Calls ==
	//		//
−
−	~~__FORCETOC__~~

@@ Line 9: / Line 9: @@
 # '''The writing must have a 2nd person point of view''' - The game's writing style is a 2nd person point of view, as such writing submissions must match that or have a very good reason why they are not (such as writing submissions for C.U.M Box shows).
 # '''I am willing to do minor coding additions to submissions but not major ones''' - Inevitably, there will be times when it is necessary for me to do coding work to make writing submissions work. I do not expect the people offering writing submissions to have coding experience, or understand the Twine/Sugarcube engine/format. However, where coding is necessary it is preferable for the coding to be minor (such as linking the scene up, exp additions, minor existing item gains, description calls, etc.) rather than major ones (such as creation of new items, new in-game transformations, mini-games, complex variables to control NPC's, etc.). I'm happy to get a scene functional, but would turn down scenes that require that excessive coding/editing workload.
 If all of that sounds reasonable to you, then good luck with your writing!

@@ Line 9: / Line 9: @@
 # '''The writing must have a 2nd person point of view''' - The game's writing style is a 2nd person point of view, as such writing submissions must match that or have a very good reason why they are not (such as writing submissions for C.U.M Box shows).
 # '''I am willing to do minor coding additions to submissions but not major ones''' - Inevitably, there will be times when it is necessary for me to do coding work to make writing submissions work. I do not expect the people offering writing submissions to have coding experience, or understand the Twine/Sugarcube engine/format. However, where coding is necessary it is preferable for the coding to be minor (such as linking the scene up, exp additions, minor existing item gains, description calls, etc.) rather than major ones (such as creation of new items, new in-game transformations, mini-games, complex variables to control NPC's, etc.). I'm happy to get a scene functional, but would turn down scenes that require that excessive coding/editing workload.
 If all of that sounds reasonable to you, then good luck with your writing!

@@ Line 16: / Line 16: @@
 == Specific Description Calls ==
 //
 __FORCETOC__

← Older revision		Revision as of 12:28, 3 October 2022
Line 18:		Line 18:
	//		//

−	~~=== Test ===~~
	//		//
		+
		+	__FORCETOC__

@@ Line 18: / Line 18: @@
 //
-== Test ==
+=== Test ===
 //

← Older revision		Revision as of 12:27, 3 October 2022
Line 16:		Line 16:

	== Specific Description Calls ==		== Specific Description Calls ==
		+	//
		+
		+	== Test ==
	//		//