Files
Bubberstation/code/__DEFINES
san7890 b679cbce96 Doc The World (Of Accesses) - The Main Bits (#68831)
Hey there,

One day, I became fed up of how dogshit it was for accesses. You would say fifty different things and find out you were wrong every time. So, I sat down today and went through and docced every single _station_ access and what it discretely did. If something wasn't true, it's not in here anymore. If it doesn't say it does something in the comment, it probably does not do it (unless I missed something poring through the code). This should be the main gist of everything, and it's much better than what we already had. As an example, ACCESS_LAWYER != ACCESS_COURT, you need to give both to the Lawyer job, or plan out those accesses accordingly when you map. It also helps when you wanna add something that only one specific job might have, because the names range from "self-explanatory" to "what?".
2022-07-29 15:51:48 +03:00
..
2022-04-17 01:21:39 -04:00
2022-04-01 21:07:46 -04:00
2022-06-26 20:48:44 -04:00
2022-07-24 16:18:59 +01:00
2022-06-16 22:36:10 +01:00
2022-04-18 09:33:32 -04:00
2022-07-23 18:05:30 -04:00
2022-07-17 01:55:12 -07:00
2022-04-27 19:38:19 +02:00
2022-07-24 16:18:59 +01:00
2022-04-17 20:06:43 -07:00
2022-04-30 17:49:54 +12:00
2022-07-17 17:47:02 -07:00
2022-06-24 17:01:45 -07:00
2022-06-01 09:25:27 +12:00
2022-01-23 14:30:27 -08:00
2022-04-08 22:25:17 -07:00

This folder is full of #define statements. They are similar to constants, but must come before any code that references them, and they do not take up memory the way constants do.

The values in this folder are NOT options. They are not for hosts to play with. Some of the values are arbitrary and only need to be different from similar constants; for example, the genetic mutation numbers in genetics.dm mean nothing, but MUST be distinct.

It is wise not to touch them unless you understand what they do, where they're used, and most importantly, how to undo your changes if you screw it up.

  • Sayu