ZXDTLZJBYTJLXWXDG2FIYIKL3LTVLRNRJQEE7GIMYB3Z37MYGGNAC RY7SCPMONZGLI3UEAQX7HDLIO36IMH65HUQRJT2IZC2FW42HPEOQC POWALBJB2MVKCUEGLHXCZWWQTNAEP7I4IQBIWB32GIOTLTXGKD2AC CZ75J5XVD2PTAPK67BUL4QY2RDBGRLITYX3SOLXUJ2UFD5CCVRCQC FS2ITYYHBLFT66YUC3ENPFYI2HOYHOVEPQIN7NQR6KF5MEK4NKZAC A4OAUGCI4B4DW4CQKAUDWIJX2556XN4DSDZYUWBYW3UDSW5YFFYQC IDGP4BJZTKAD6ZO4RLAWYVN6IFCMIM76G6HJGPTE27K4D6CDBUHQC IXHSSD6U2EAJA5TJWC3UQ45XQHZVUWRU3GOIF43XJ6YPSWNPDO5QC VCF6NJ5REA6CBIHJDKP4DVGKHG5CILQ77IHGYE2QPB4ANFHE5TKAC A2TQYJ6JZJF2T47C26H2IRSR6O67BP6VHY5PV7GTFG4IZNQQBJVQC * This approach puts one top-level definition per file, and so obscures theorder in which definitions are loaded. In particular, initializing a globaltable to contain other global definitions will fail if you originallyauthored the other global definitions after the table.I never initialize global tables with other definitions. That kind of thinghappens in `on.initialize` (akin to `love.load`; see reference.md) or`on.code_change`.