I’ve inherited a set of three nodeGame games someone else wrote that
I’ve been asked to resuscitate. I seem to have gotten them working
fine, finally, but they’re each still spitting out a pair of warnings
when the launcher is started, for example (this is in nodeGame
v7.1.0):
| 2022-03-28T21:09:14.036Z warn: GameLoader.buildRequirementsConf: no
requirements directory. Game: GroupInvestment2. Level: game_proper
| 2022-03-28T21:09:14.050Z warn: GameLoader.loadAuthDir: channel
GroupInvestment2: authorization disabled in configuration file
| Requirements room created: GroupInvestment2
There IS a requirements/ directory, it contains
| dfm@janus:/home/ddmlab/experiments/nodegame/games_available/investment/GroupInvestment2/requirements$
ls
| total 16K
| -rw-rw-r-- 1 dfm ddmlab 3.7K Mar 25 08:13 requirements.js.sample
| -rw-rw-r-- 1 dfm ddmlab 4.2K Mar 25 08:13 requirements.room.js.sample
| -rw-rw-r-- 1 dfm ddmlab 3.3K Mar 25 08:13 requirements.settings.js
It not clear to me which configuration file I should be looking in for
the second warning. In particular, there appear to be no files
anywhere that contain the string “config”:
| dfm@janus:/home/ddmlab/experiments/nodegame/games_available/investment/GroupInvestment2$
find . -name '*config*'
| dfm@janus:/home/ddmlab/experiments/nodegame/games_available/investment/GroupInvestment2$
While APPARENTLY harmless, it seems it would be good to understand
them and make them go away. Any thoughts on what these warnings are
telling me I should fix, please?
Thanks!
--
Don Morrison <
d...@ringing.org>
“I did not sit down to write a scripting language that would be used
by 9 million domains: I sat down to solve a problem. Solving the
problem by 5pm so you can go to a movie with your girlfriend leads to
some aspects that aren’t ideal 7 years later, when thousands of people
have to work around that late-night hack you added.”
– Rasmus Lerdorf, the creator of PHP,
in an interview with SitePoint, 22 May 2002