ModError: Failed to load and run script from /home/<username>/.minetest/games/voxelforge/mods/CORE/vlf_json/init.lua:
...r/.minetest/games/voxelforge/mods/CORE/vlf_json/init.lua:70: Invalid JSON data in file: nodes.json
stack traceback:
[C]: in function 'error'
...r/.minetest/games/voxelforge/mods/CORE/vlf_json/init.lua:70: in function 'register_nodes_from_json'
...r/.minetest/games/voxelforge/mods/CORE/vlf_json/init.lua:106: in main chunk
Gregon. First of all. I'm trying to keep the mod naming consistant with the game name, also renaming will introduce numerous bugs as it did the first time, and that will take weeks to fix(also like last time), so I'm sorry, but I will not be doing that. Though in the future there will be a compat update. Though for nodes items, and entities, not modnames.
As to the crashing. May I ask which version of VoxelForge you are using ? I can't seem to reproduce the crash on any of the 4 latest versions.
I use latest version (alpha 0.4.0). I tested nodes.json and items.json files in first online json validator that I found and they was not valid (there was comma before "}"), I deleted comma in that files, and it started working, but there still was many bugs:
I don't know how you had a comma before the bracket ('}') None of the latest VoxelForge versions have that.
Font size is controlled by settings. So not a bug, that chat size is default However. You can go to settings/VoxelForge/graphics then you'll see a bunch of fontsize settings.
Those errors I am aware of. It's due to one overall bug. Which I have already fixed, it's just not in the newest release. Though I suppose I should open an issue on git, so everyone knows I'm aware of it. Anyway. next release will have the fix.
And before anyone else reports this issue. after playing VoxelForge and then playing another game it says failed to load font ''. and that it's going to use the fallback.
Edit: I have checked thoroughly, (multiple times) and I can't find any case of a comma before any brackets '}' in any of the recent versions. Or any of the versions at all for that matter. I'm not sure how that comma got there. I'll leave the issue on github open, and if anyone else has this same issue, please report it.
For those that don't have github accounts you can post your suggestions here.
Can you please rename all names back to mcl, to support mods for Mineclonia?
Also, when I start game, it crashes:
Gregon. First of all. I'm trying to keep the mod naming consistant with the game name, also renaming will introduce numerous bugs as it did the first time, and that will take weeks to fix(also like last time), so I'm sorry, but I will not be doing that. Though in the future there will be a compat update. Though for nodes items, and entities, not modnames.
As to the crashing. May I ask which version of VoxelForge you are using ? I can't seem to reproduce the crash on any of the 4 latest versions.
Also please provide steps for reproducing.
I use latest version (alpha 0.4.0). I tested nodes.json and items.json files in first online json validator that I found and they was not valid (there was comma before "}"), I deleted comma in that files, and it started working, but there still was many bugs:
I don't know how you had a comma before the bracket ('}') None of the latest VoxelForge versions have that.
Font size is controlled by settings. So not a bug, that chat size is default However. You can go to settings/VoxelForge/graphics then you'll see a bunch of fontsize settings. Those errors I am aware of. It's due to one overall bug. Which I have already fixed, it's just not in the newest release. Though I suppose I should open an issue on git, so everyone knows I'm aware of it. Anyway. next release will have the fix.
And before anyone else reports this issue. after playing VoxelForge and then playing another game it says failed to load font ''. and that it's going to use the fallback.
Edit: I have checked thoroughly, (multiple times) and I can't find any case of a comma before any brackets '}' in any of the recent versions. Or any of the versions at all for that matter. I'm not sure how that comma got there. I'll leave the issue on github open, and if anyone else has this same issue, please report it.