Changelog - Revision history

Skizzerz: /* 4.2.0 */

2021-06-15T03:03:37Z

4.2.0

Skizzerz: add 4.2.0 changelog

2021-06-15T03:01:27Z

add 4.2.0 changelog

Skizzerz at 06:06, 26 December 2019

2019-12-26T06:06:53Z

Skizzerz at 05:51, 26 December 2019

2019-12-26T05:51:42Z

Skizzerz: /* 4.0.0 */

2018-12-23T17:58:10Z

4.0.0

Skizzerz: /* 4.0.0 */ update

2018-12-23T17:54:31Z

4.0.0: update

Skizzerz at 05:02, 23 December 2018

2018-12-23T05:02:06Z

Skizzerz at 01:54, 23 December 2018

2018-12-23T01:54:19Z

Skizzerz: /* 3.2.0 */

2018-03-26T16:56:51Z

3.2.0

Skizzerz at 20:41, 23 March 2018

2018-03-23T20:41:03Z

@@ Line 6: / Line 6: @@
 New user features:
-* The rerollN() function now accepts any numerical expression for the first argument (max # of rerolls) e.g. {{c|1d20.rerollN(2+3, =1)}} or {{c|1d20.rerollN(1d6, =1)}}
+* The rerollN() function now accepts any numerical expression for the first argument (max # of rerolls) e.g. {{c|1=1d20.rerollN(2+3, =1)}} or {{c|1=1d20.rerollN(1d6, =1)}}
-* The rerollN() function can now be specified multiple times for fine-grained reroll control, e.g. {{c|1d20.rerollN(2, =1).rerollN(1, =2, =3)}} rerolls either a "2" or "3" once but rerolls a "1" twice.
+* The rerollN() function can now be specified multiple times for fine-grained reroll control, e.g. {{c|1=1d20.rerollN(2, =1).rerollN(1, =2, =3)}} rerolls either a "2" or "3" once but rerolls a "1" twice.
 * More informative error messages if you omit something when specifying an extra on a roll
 * Dice expressions are no longer case sensitive. Roll 1d20 or 1D20, whichever you prefer!

← Older revision		Revision as of 03:01, 15 June 2021
Line 1:		Line 1:
	<div class="nonumtoc">__TOC__</div>		<div class="nonumtoc">__TOC__</div>
		+
		+	== 4.2.0 ==
		+	Backwards-incompatible changes:
		+	* Some DiceAST subclasses were removed. The DiceAST class hierarchy is considered an implementation detail and not a public API for the purposes of semantic versioning. However, the change is being noted here so any library consumers incorrectly casting to or using these subclasses can audit their code.
		+
		+	New user features:
		+	* The rerollN() function now accepts any numerical expression for the first argument (max # of rerolls) e.g. {{c\|1d20.rerollN(2+3, =1)}} or {{c\|1d20.rerollN(1d6, =1)}}
		+	* The rerollN() function can now be specified multiple times for fine-grained reroll control, e.g. {{c\|1d20.rerollN(2, =1).rerollN(1, =2, =3)}} rerolls either a "2" or "3" once but rerolls a "1" twice.
		+	* More informative error messages if you omit something when specifying an extra on a roll
		+	* Dice expressions are no longer case sensitive. Roll 1d20 or 1D20, whichever you prefer!
		+	* Defining a success condition is no longer required when all you want to do is define a failure (negative success) condition
		+	* New function explodeOnce() / !eo to perform an explode operation at most once.
		+	* New function implode() / !i to act as the inverse of explode; when the comparison is met a new die is rolled and subtracted from the result. This continues until the comparison fails.
		+	* New function implodeOnce() / !io to perform an implode operation at most once.
		+	* New function compoundImplode() to perform an implode operation with compound semantics, causing a single die to be sent as output containing the final result of the implode operation.
		+
		+	New developer features:
		+	* Builtin functions can be overridden by custom functions by registering a function with the same name
		+	* Builtin functions can be removed
		+	* Custom functions can be registered with the same timing as builtin functions
		+	* Custom extras can be registered along with custom functions
		+	* Custom functions can specify how multiples of the same function are executed when attached to the same roll
		+	* Custom functions can specify how their arguments should look, and will be validated before being called
		+	* XML documentation added to all classes, methods, and properties for better IntelliSense. Improving the XML documentation quality is still a work in progress, please leave suggestions in a new issue on GitHub!
		+
		+	Bugfixes:
		+	* Fixed nullability annotation for {{l\|Dice.DieResult.Data\|DieResult.Data}}; this string can be nullable and has always defaulted to null
		+
		+	Deprecations:
		+	* {{l\|Dice.BuiltinFunctions}} and {{l\|Dice.BuiltinMacros}} are deprecated; please use their counterparts in the Dice.Builtins namespace if you would like to directly call any of them from within your custom functions/macros. These two classes will be removed in the next major release.
		+	* DiceErrorCode.InvalidSuccess is deprecated and no longer used by the library. This enum value will be removed in the next major release.
		+	* Direct access to the DiceAST classes and the parser is deprecated; these will become inaccessible or transition to using a public interface instead of exposing the classes directly in the next major release. No deprecation notice is emitted while compiling for these deprecations.
		+	* .NET Framework 4.5.2 support is deprecated; support will be dropped when .NET Framework 4.5.2 reaches end of support from Microsoft on April 26, 2022. Circumstances in the future may cause an earlier removal.

	== 4.1.0 ==		== 4.1.0 ==

@@ Line 9: / Line 9: @@
 * Bugfixes:
 ** None
 == 4.0.0 ==

← Older revision		Revision as of 05:51, 26 December 2019
Line 1:		Line 1:
	<div class="nonumtoc">__TOC__</div>		<div class="nonumtoc">__TOC__</div>
		+
		+	== 4.1.0 ==
		+	* Backwards-incompatible changes:
		+	** None
		+	* New features:
		+	** The leading number denoting number of dice (before the "d") is optional and will default to 1 if not specified.
		+	** Nullability annotations have been added to public APIs, to assist developers in migrating their own applications using this library.
		+	* Bugfixes:
		+	** None

	== 4.0.0 ==		== 4.0.0 ==

@@ Line 12: / Line 12: @@
 ** A new property {{l|Dice.RollerConfig.RollDie|RollerConfig.RollDie}} was added to allow customizing the result of a die roll in a more friendly way. This property is a callback which receives the minimum and maximum value it can roll for a die, and should return a number within that range. By default, it will call {{l|Dice.RollerConfig.GetRandomBytes|RollerConfig.GetRandomBytes}} repeatedly until it gets a result it can transform into the output range without introducing any bias.
 ** New APIs {{l|Dice.Roller.Max|Roller.Max()}}, {{l|Dice.Roller.Min|Roller.Min()}}, and {{l|Dice.Roller.Average|Roller.Average()}} evaluate the dice expression and return the result as if all dice rolled their minimum, maximum, or average values.
 * Dependency updates:
 ** Updated Antlr4.Runtime.Standard from 4.7.1 to 4.7.2

@@ Line 9: / Line 9: @@
 ** Success/failure rolls can now be decorated with critical/fumbles. A critical success (a roll that is both a critical and a success) is worth 2 successes, and a critical failure (a roll that is both a fumble and a failure) is worth -2 successes. This expands support into game systems which use success-based rolls but have varying degrees of success beyond just +1 or -1.
 *** Unless a success/failure roll is explicitly decorated with a critical/fumble, those rolls will not be marked as criticals or fumbles even if the max or min amount is rolled. This keeps default behavior with such rolls consistent with how they worked previously.
-** A new [[Dice Reference#numdice|{{c|[numDice]}}]] macro was added, which returns the total number of dice rolled up to this point.
+** A new [[Dice Reference#numdice|{{c|[numDice]}}]] macro was added, which returns the total number of dice rolled up to this point. This macro is available in all scenarios, including the stand-alone {{l|Dice.Roller.Roll|Roller.Roll}}; using the Play-by-Post helper is not required to use this macro.
-** New APIs {{l|Dice.Roller.Max|Roller.Max()}}, {{l|Dice.Roller.Min|Roller.Min()}}, and {{l|Dice.Roller.Average|Roller.Average()}} evaluate the dice expression and return the maximum, minimum, or average result.
+** A new property {{l|Dice.RollerConfig.RollDie|RollerConfig.RollDie}} was added to allow customizing the result of a die roll in a more friendly way. This property is a callback which receives the minimum and maximum value it can roll for a die, and should return a number within that range. By default, it will call {{l|Dice.RollerConfig.GetRandomBytes|RollerConfig.GetRandomBytes}} repeatedly until it gets a result it can transform into the output range without introducing any bias.
 * Dependency updates:
 ** Updated Antlr4.Runtime.Standard from 4.7.1 to 4.7.2

@@ Line 1: / Line 1: @@
 <div class="nonumtoc">__TOC__</div>
-== 3.2.0 ==
+== 4.0.0 ==
 * New features:
 ** DiceRoller is now packaged for both .NET Standard 2.0 as well as .NET Framework 4.5.2. .NET Standard 2.0 supports .NET Framework 4.6.1+ and .NET Core 2.0.