@faraday said in Population Code:
Like weather code, it seems like something that would easily be forgotten and/or ignored, and just cause people RPing inconsistently.
This term has entered my RP vocabulary: "Are we RPing time/weather?" Almost every game I've RP'd on since the banishment of the dreaded "Nightzone" flag has had people either RPing game time or clarifying the conditions in their initial pose.
@acceleration: Do it if you think it'd be fun to do. I've long ago learned that doing something expecting it to only have value if it's used is not going to leave a good taste in your mouth, as what Mushers value is not consistent and doesn't always make sense. I have about half-finished a weather system that is independent from the real world, mostly because it was a challenge. What I got out of it was a single function, 'ictime()', that can give the builders all the information they want for day/night/moon phase/weather/season @descs.
This in turn gave me the grounding to make a function-based 'places()' code which far surpasses the traditional places code. I've written a lot of code that was never really used, but I knew that going into it.
Your question makes more sense when you're coding for any particular game. This is the occasion where you're being asked to code something, and you need to find out: Does this add usable code to the game? If the answer is "no" then see above; you're coding for fun. If the answer is "yes", then don't worry if other games will use it.
This is why my answer was convoluted. Before I can say if I'd use it, I'd want to know what it's useful for or, at least, an overview of how it works. I can see the footer for a room not only having a location's security ("Poor"), but its current population ("~7 NPCs here").