Files
Bubberstation/code/__DEFINES
AnturK 84f69359a0 More horrible 515 proc compatibility. (#71333)
So i left over some basic `/whatever/proc/format` uses in the original
PR this fixes it.

Notable exceptions to the rule:
- Paths in add_verb/remove_verb, we need full path instead of a name
there to access verb metadata so we can't use proc ref macros there.
- regex.Replace, found out that it does not accept call by name. Instead
i added new REGEX_REPLACE_HANDLER so we can at least try to mark these.

There's still leftover global procs that do not use GLOBAL_PROC_REF but
they functionally equivalent so that's for later.

I don't see any reasonable way to grep for this. But if you got any
ideas please share.
2022-11-22 07:55:43 +00:00
..
2022-11-20 23:18:30 -08:00
2022-11-19 21:23:28 +00:00
2022-06-26 20:48:44 -04:00
2022-11-15 03:50:11 +00:00
2022-08-25 20:13:36 -07:00
2022-04-18 09:33:32 -04:00
2022-11-19 14:27:10 -08:00
2022-11-19 14:27:10 -08:00
2022-11-07 16:22:37 -08:00
2022-09-28 11:54:22 -07:00
2022-10-12 19:57:04 -07:00
2022-07-24 16:18:59 +01:00
2022-11-18 16:42:28 +13:00
2022-09-02 10:13:43 +12:00
2022-08-19 21:39:58 -07:00
2022-11-01 11:45:57 +13:00
2022-11-20 23:18:30 -08:00
2022-11-20 23:22:46 -08:00
2022-10-29 13:54:30 -05:00
2022-11-04 01:23:23 -07:00
2022-11-19 14:27:10 -08: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