The output of MinecraftStats (the data directory) is created in the current working directory, not where update.py or the config file is located. This regularly seems to confuse users when working with cronjobs (e.g., #134, #122, #104).
This kind of behaviour is completely standard and can be very useful (e.g., when working with multiple servers on the same machine), so I have no intentions to change it. The only idea that I have is giving a proper example in the documentation paragraph mentioning cron jobs.
The output of MinecraftStats (the
datadirectory) is created in the current working directory, not whereupdate.pyor the config file is located. This regularly seems to confuse users when working with cronjobs (e.g., #134, #122, #104).This kind of behaviour is completely standard and can be very useful (e.g., when working with multiple servers on the same machine), so I have no intentions to change it. The only idea that I have is giving a proper example in the documentation paragraph mentioning cron jobs.