Open shennetsind opened 10 years ago
in my opinion, It should be stored in one place, and whatever else that may need to store it differently reads from that place and stores it differently, not cache it differently all over the place as is being done.
agree in centralization and I suggest to store it in const.txt
Doesn't really belong to performance but I didn't feel well on another milestone, anyway: Its all over the place, really. By aggregating it smartly we could duck hundreds of lines of code and make the whole process of adding or modifying job data waaaay more flexible (and thus faster). Glance job names:
...
... (char-server)
...
...
... (the following could even get out of the file and populated during runtime by the server using the centralized data)