godot-fmod - Godot with FMOD integration

Age	Commit message (Collapse)	Author
2023-01-30	Add option to print filenames in GDScript unit testing	ocean (they/them)

2023-01-05	One Copyright Update to rule them all	Rémi Verschelde
	As many open source projects have started doing it, we're removing the current year from the copyright notice, so that we don't need to bump it every year. It seems like only the first year of publication is technically relevant for copyright notices, and even that seems to be something that many companies stopped listing altogether (in a version controlled codebase, the commits are a much better source of date of publication than a hardcoded copyright statement). We also now list Godot Engine contributors first as we're collectively the current maintainers of the project, and we clarify that the "exclusive" copyright of the co-founders covers the timespan before opensourcing (their further contributions are included as part of Godot Engine contributors). Also fixed "cf." Frenchism - it's meant as "refer to / see".
2022-07-25	Code quality: Fix header guards consistency	Rémi Verschelde
	Adds `header_guards.sh` bash script, used in CI to validate future changes. Can be run locally to fix invalid header guards.
2022-06-29	Adding print_rich for printing with BBCode	Voylin

2022-04-04	Zero initialize all pointer class and struct members	Rémi Verschelde
	This prevents the pitfall of UB when checking if they have been assigned something valid by comparing to nullptr.
2022-01-03	Update copyright statements to 2022	Rémi Verschelde
	Happy new year to the wonderful Godot community!
2021-10-14	Implement toast notifications in the editor	Gilles Roudière

2021-04-08	Add runner for GDScript testing	George Marques
	This is meant for testing the GDScript implementation, not for testing user scripts nor testing the engine using scripts. Tests consists in a GDScript file and a .out file with the expected output. The .out file format is: expected status (based on the enum GDScriptTest::TestStatus) on the first line, followed by either an error message or the resulting output. Warnings are added after the first line, before the output (or compiler errors) if the parser pass without any error. The test script must have a function called `test()` which takes no argument. Such function will be called by the test runner. The test should not have any dependency unless it's part of the test too. Global classes (using `class_name`) are registered before the runner starts, so those should work if needed. Use the command `godot --gdscript-generate-tests godot-source/modules/gdscript/tests/scripts` to update the .out files with the current output (make sure the output are the expected values before committing). The tests themselves are part of the doctest suite so those can be executed with `godot --test`. Co-authored-by: Andrii Doroshenko (Xrayez) <xrayez@gmail.com>