RDCode - Revision history

Camellia258: minor typo fix

2026-03-09T17:12:28Z

minor typo fix

← Older revision		Revision as of 17:12, 9 March 2026
Line 1:		Line 1:
	'''RDCode''' (abbreviation of ''Rhythm Doctor Code'') is the set of features in Rhythm Doctor that encompass Custom Methods, Tags, Conditionals, and simple programming via reading and writing to variables. ~~Hereinelsewhere~~ and in the community, the word "'''''RDCode'''''" on its own usually refers to its programming language.		'''RDCode''' (abbreviation of ''Rhythm Doctor Code'') is the set of features in Rhythm Doctor that encompass Custom Methods, Tags, Conditionals, and simple programming via reading and writing to variables. Here and elsewhere and in the community, the word "'''''RDCode'''''" on its own usually refers to its programming language.

	Note that all RDCode is affected by the player's '''Visual Offset''', which can cause timing issues in certain cases.		Note that all RDCode is affected by the player's '''Visual Offset''', which can cause timing issues in certain cases.

Azabiphetamine at 11:47, 7 March 2025

2025-03-07T11:47:31Z

← Older revision		Revision as of 11:47, 7 March 2025
Line 25:		Line 25:
	To add a tag to an event, click on the "''Bar''" text in the top of the Event window, and it will turn into a "''Tag''" textbox.		To add a tag to an event, click on the "''Bar''" text in the top of the Event window, and it will turn into a "''Tag''" textbox.
	<!--It's best practice to encompass individual and separate tags in square brackets (<code>[]</code>).-->		<!--It's best practice to encompass individual and separate tags in square brackets (<code>[]</code>).-->

	See [[List_of_Custom_Methods#Tags\|List of Tags]] for a set of special tags that can't be affected by Tag Action but rather are handled by game input.		See [[List_of_Custom_Methods#Tags\|List of Tags]] for a set of special tags that can't be affected by Tag Action but rather are handled by game input.

Azabiphetamine at 11:47, 7 March 2025

2025-03-07T11:47:16Z

← Older revision		Revision as of 11:47, 7 March 2025
Line 25:		Line 25:
	To add a tag to an event, click on the "''Bar''" text in the top of the Event window, and it will turn into a "''Tag''" textbox.		To add a tag to an event, click on the "''Bar''" text in the top of the Event window, and it will turn into a "''Tag''" textbox.
	<!--It's best practice to encompass individual and separate tags in square brackets (<code>[]</code>).-->		<!--It's best practice to encompass individual and separate tags in square brackets (<code>[]</code>).-->
			See [[List_of_Custom_Methods#Tags\|List of Tags]] for a set of special tags that can't be affected by Tag Action but rather are handled by game input.

	== Conditionals ==		== Conditionals ==

Azabiphetamine at 11:40, 7 March 2025

2025-03-07T11:40:38Z

← Older revision		Revision as of 11:40, 7 March 2025
Line 1:		Line 1:
	'''RDCode''' (abbreviation of ''Rhythm Doctor Code'') is the set of features in Rhythm Doctor that encompass ~~[[Call Custom Method\|~~Custom Methods]], ~~[[Tag Action\|~~Tags]], ~~conditionals~~, and simple programming via reading and writing to variables. Hereinelsewhere and in the community, the word "'''''RDCode'''''" on its own usually refers to its programming language.		'''RDCode''' (abbreviation of ''Rhythm Doctor Code'') is the set of features in Rhythm Doctor that encompass Custom Methods, Tags, Conditionals, and simple programming via reading and writing to variables. Hereinelsewhere and in the community, the word "'''''RDCode'''''" on its own usually refers to its programming language.

			Note that all RDCode is affected by the player's '''Visual Offset''', which can cause timing issues in certain cases.

	== Custom Methods ==		== Custom Methods ==

	See [[Call Custom Method]].		'''Custom Methods''' are functions that can be executed for various uses, whether to manage audio, VFX, gameplay, or specific built-in cases like a ''Gameover'' or custom ''Rank'' screen.

			See [[Call Custom Method]] for how to execute Custom Methods and [https://docs.google.com/spreadsheets/d/1JAz6iRLqcn08ZeTeBHeeDrpdX6M5K0b1qRVQomua21s/edit List of Custom Methods] for a list of the available ones.

			'''''Note that Custom Methods are not officially endorsed to be used by the devs, and can break anytime when the game updates.'''''

	=== Comment Commands ===		=== Comment Commands ===
Line 11:		Line 17:
	== Tags ==		== Tags ==

	~~See [[Tag Action]] and [[Call Custom Method]]~~.		'''Tags''' can be set on events to run them at any time, in order. If an event or series of events are tagged, they will run whenever the tag is run. This is useful for looping the same events or running them based on player inputs or choices (i.e. not bound to a specific beat nor bar).

	~~To add a tag to an event~~, ~~click~~ on the ~~"''Bar~~''~~" text~~ in the ~~top of~~ the ~~Event window,~~ and it will ~~turn into~~ a ~~"''Tag''" textbox~~.		Tagged events only run at the same time if, on the timeline, they're placed on the same beat and bar. They're run in order, such that if a tagged event is placed on beat 1 and another on beat 2, when running the tag, the first event will run immediately and there will be a 1 beat delay to the next event. <!-- ive no idea how to word this better if anyone could check it thanks -->

	~~It's best practice to encompass individual~~ and ~~separate~~ tags ~~in square brackets~~ (~~<code>~~[]~~</code>~~).		See [[Tag Action]] for running and managing tags. ([[Call Custom Method]] also has a set of Custom Methods that equate to Tag Action's functionality.)

			To add a tag to an event, click on the "''Bar''" text in the top of the Event window, and it will turn into a "''Tag''" textbox.
			<!--It's best practice to encompass individual and separate tags in square brackets (<code>[]</code>).-->
	== Conditionals ==		== Conditionals ==

Azabiphetamine: /* Custom */

2025-02-06T11:23:38Z

Custom

← Older revision		Revision as of 11:23, 6 February 2025
Line 50:		Line 50:

	'''Custom''' conditionals allow for '''RDCode''' conditional expressions to be inputted, such as comparisons (e.g. <code>i0 < 5</code>) and boolean reading (e.g. <code>b0</code>).		'''Custom''' conditionals allow for '''RDCode''' conditional expressions to be inputted, such as comparisons (e.g. <code>i0 < 5</code>) and boolean reading (e.g. <code>b0</code>).

			See [[List of Custom Methods#Variables\|List of Variables]] for variables that can be checked within these types of conditionals.

	== RDCode programming ==		== RDCode programming ==

Azabiphetamine: rdcode var reading since many events allow it

2025-02-06T11:16:54Z

rdcode var reading since many events allow it

← Older revision		Revision as of 11:16, 6 February 2025
Line 64:		Line 64:

	Note that, when converting between data types (e.g. <code>i0 = f0</code>, <code>b0 = i0</code>), floats will be '''rounded''' (0.5 rounding is inconsistent, can be upwards or downwards), and integers to booleans will return '''false''' if its equal to 0, otherwise '''true'''.		Note that, when converting between data types (e.g. <code>i0 = f0</code>, <code>b0 = i0</code>), floats will be '''rounded''' (0.5 rounding is inconsistent, can be upwards or downwards), and integers to booleans will return '''false''' if its equal to 0, otherwise '''true'''.

			Certain events that have text-boxes are able to read these 30 variables, using curly brackets (<code>{}</code>), and having inside a valid RDCode arithmetic expression. (e.g. in a [[Floating Text]] event, <code>Current score: {i0}</code> will display the current value of <code>i0</code>).

	There are '''non-readable but writeable''' variables that affect gameplay and visuals, and they're only able to be used in '''[[Call Custom Method]]''' events. E.g. <code>wobblyLines</code> (bool), <code>noHitFlashBorder</code> (bool), and <code>room[]</code> (this is a special '''array''' variable that can accept custom methods that affect individual rooms). See [https://docs.google.com/spreadsheets/d/1JAz6iRLqcn08ZeTeBHeeDrpdX6M5K0b1qRVQomua21s/edit List of Custom Methods] for a further list.		There are '''non-readable but writeable''' variables that affect gameplay and visuals, and they're only able to be used in '''[[Call Custom Method]]''' events. E.g. <code>wobblyLines</code> (bool), <code>noHitFlashBorder</code> (bool), and <code>room[]</code> (this is a special '''array''' variable that can accept custom methods that affect individual rooms). See [https://docs.google.com/spreadsheets/d/1JAz6iRLqcn08ZeTeBHeeDrpdX6M5K0b1qRVQomua21s/edit List of Custom Methods] for a further list.

Azabiphetamine: list redirect until page exists

2025-02-05T09:42:55Z

list redirect until page exists

← Older revision		Revision as of 09:42, 5 February 2025
Line 65:		Line 65:
	Note that, when converting between data types (e.g. <code>i0 = f0</code>, <code>b0 = i0</code>), floats will be '''rounded''' (0.5 rounding is inconsistent, can be upwards or downwards), and integers to booleans will return '''false''' if its equal to 0, otherwise '''true'''.		Note that, when converting between data types (e.g. <code>i0 = f0</code>, <code>b0 = i0</code>), floats will be '''rounded''' (0.5 rounding is inconsistent, can be upwards or downwards), and integers to booleans will return '''false''' if its equal to 0, otherwise '''true'''.

	There are '''non-readable but writeable''' variables that affect gameplay and visuals, and they're only able to be used in '''[[Call Custom Method]]''' events. E.g. <code>wobblyLines</code> (bool), <code>noHitFlashBorder</code> (bool), and <code>room[]</code> (this is a special '''array''' variable that can accept custom methods that affect individual rooms). See [[List of Custom Methods]] for a further list.		There are '''non-readable but writeable''' variables that affect gameplay and visuals, and they're only able to be used in '''[[Call Custom Method]]''' events. E.g. <code>wobblyLines</code> (bool), <code>noHitFlashBorder</code> (bool), and <code>room[]</code> (this is a special '''array''' variable that can accept custom methods that affect individual rooms). See [https://docs.google.com/spreadsheets/d/1JAz6iRLqcn08ZeTeBHeeDrpdX6M5K0b1qRVQomua21s/edit List of Custom Methods] for a further list.

	Finally, there are '''non-writeable''' variables that can still be read and used only in '''conditionals''', such as <code>autoplay</code> (bool), <code>levelSpeed</code> (float), and <code>numMistakes</code> (float).		Finally, there are '''non-writeable''' variables that can still be read and used only in '''conditionals''', such as <code>autoplay</code> (bool), <code>levelSpeed</code> (float), and <code>numMistakes</code> (float).

Azabiphetamine: comment commands

2025-01-29T09:58:13Z

comment commands

← Older revision		Revision as of 09:58, 29 January 2025
Line 4:		Line 4:

	See [[Call Custom Method]].		See [[Call Custom Method]].

			=== Comment Commands ===

			See [[Comment#Advanced\|Comment]].

	== Tags ==		== Tags ==

Azabiphetamine: oops

2025-01-21T16:36:17Z

oops

← Older revision		Revision as of 16:36, 21 January 2025
Line 37:		Line 37:
	=== Player Mode ===		=== Player Mode ===

	'''Player Mode''' allows the detection of '''1-player''' or '''2-player''' within the same level file (useful in case '''both modes''' is selected in export settings and a different '''2-player''' file is not provided). Note that in the editor, if the player changes from 1-player to 2-player during playback, the "player mode" state (1P/2P) ~~'''~~will ~~not switch'''~~.		'''Player Mode''' allows the detection of '''1-player''' or '''2-player''' within the same level file (useful in case '''both modes''' is selected in export settings and a different '''2-player''' file is not provided). Note that in the editor, if the player changes from 1-player to 2-player during playback, the "player mode" state (1P/2P) will update accordingly.

	=== Language ===		=== Language ===

Raf13lol: no more Durations, durations is here

2025-01-17T19:00:58Z

no more Durations, durations is here

← Older revision		Revision as of 19:00, 17 January 2025
Line 23:		Line 23:
	Conditionals have a ''Tag'' (text identifier), ''ID'' (unique numerical identifier), and ''Name'' (text that appears in the conditional (select) list).		Conditionals have a ''Tag'' (text identifier), ''ID'' (unique numerical identifier), and ''Name'' (text that appears in the conditional (select) list).

	Events can also have set '''~~Durations~~'''. Though they aren't exclusively used in combination with conditionals, they nearly always go together. They allow an event to be triggered during a set timeframe defined by the '''~~Duration~~''' in '''beats''', as long as the conditionals are true at any point during that timeframe. E.g., setting a <code>numMistakes > 5</code> conditional alongside an 8-beat '''~~Duration~~''' will run the event when the mistake amount surpasses 5 ''at any point within those 8 beats''.		Events can also have set '''durations'''. Though they aren't exclusively used in combination with conditionals, they nearly always go together. They allow an event to be triggered during a set timeframe defined by the '''duration''' in '''beats''', as long as the conditionals are true at any point during that timeframe. E.g., setting a <code>numMistakes > 5</code> conditional alongside an 8-beat '''duration''' will run the event when the mistake amount surpasses 5 ''at any point within those 8 beats''.

	Conditionals can have multiple ''type''s:		Conditionals can have multiple ''type''s: