advtrains.git - Advtrains mod for minetest.

	Commit message (Expand)	Author	Age
*	Move passive API to the advtrains core	orwell96	2018-08-16
*	Implement routesetting	orwell96	2018-07-21
*	Fix bugs found while testing	orwell96	2018-06-14
*	Mainly make collisions and coupling work	orwell96	2018-06-14
*	Rework the privilege system completely	orwell96	2018-03-14
*	Log certain events in a logfile in the world directory	Gabriel Pérez-Cerezo	2018-02-21
*	Rewrite rail connection system...	orwell96	2017-12-18
*	Fix multiple track types not working simultaneously	orwell96	2017-11-22
*	Make trackplacer align rails by any tracks, not just by tracks with the same ...	orwell96	2017-11-22
*	Change name of the node database group in order to clone node database code i...	orwell96	2017-10-31
*	*	Remove zip release files, move mod to root, exclude assets from Makefile (#92)	rubenwardy	2017-09-20
*	Restructure mod directory	orwell96	2017-01-04
*	Add Automatic Train Control system	orwell96	- Refer to the [Lua API](https://github.com/minetest/minetest/blob/master/doc/lua_api.txt), [Developer Wiki](http://dev.minetest.net/Main_Page) and other [documentation](https://github.com/minetest/minetest/tree/master/doc). - Follow the [C/C++](http://dev.minetest.net/Code_style_guidelines) and [Lua](http://dev.minetest.net/Lua_code_style_guidelines) code style guidelines. - Check your code works as expected and document any changes to the Lua API. 4. Commit & [push](https://help.github.com/articles/pushing-to-a-remote/) your changes to a new branch (not `master`, one change per branch) - Commit messages should: - Use the present tense. - Be descriptive. See the commit messages by core developers for examples. - The first line should: - Start with a capital letter. - Be a compact summary of the commit. - Preferably have less than 70