What do new mappers think of the information available?

Average Person · May 25, 2020

Just curious if any new mappers or old mappers who aren't used to the new file format have any questions I might be able to answer or if a certain kind of tutorial would be useful to new mappers.

Aboroath · May 26, 2020

Welp, I am going to take you up on this. My main problem is with the .json format. I made a map back in 2015 with the .cs format and it quite frankly was a joy to use....almost too easy. Since the .json format was introduced I have been perplexed as to why every single .json I touch has some sort of syntax error, if that is even what it is. No matter how careful I am with the replace function in notepad++ something is wrong. Jsonlint identifies even the most simple .json file as having a syntax error yet everything is there. I will post a simple example of my issue with a simple map thumbnail that illustrates the problem visually along with the pertinent .json tomorrow.

Thank you for your generous offer!

Nadeox1 · May 26, 2020

Aboroath said: ↑

Welp, I am going to take you up on this. My main problem is with the .json format. I made a map back in 2015 with the .cs format and it quite frankly was a joy to use....almost too easy. Since the .json format was introduced I have been perplexed as to why every single .json I touch has some sort of syntax error, if that is even what it is. No matter how careful I am with the replace function in notepad++ something is wrong. Jsonlint identifies even the most simple .json file as having a syntax error yet everything is there. I will post a simple example of my issue with a simple map thumbnail that illustrates the problem visually along with the pertinent .json tomorrow.

Thank you for your generous offer!
Click to expand...

For levels, we use the standard* Json syntax.
The pros of that is that being a standard, it's syntax rules are the same, and you can use Json linters to check your files. *The one we have allows for comments, so beware whether the linter you use allows them or not.

VS Code has some great support for it (both flavors)

It is strict regarding syntax, and even missing commas will lead to problems.
May sound annoying, but forces your 'code' to be written properly, with eventually ends with cleaner code, making it more futureproof.

Old .CS was all over the place. It was not a standard and one was able to do pretty atrocious syntax hacks, which are a pain to carry around and to consider.

Average Person · May 26, 2020

Aboroath said: ↑

Welp, I am going to take you up on this. My main problem is with the .json format. I made a map back in 2015 with the .cs format and it quite frankly was a joy to use....almost too easy. Since the .json format was introduced I have been perplexed as to why every single .json I touch has some sort of syntax error, if that is even what it is. No matter how careful I am with the replace function in notepad++ something is wrong. Jsonlint identifies even the most simple .json file as having a syntax error yet everything is there. I will post a simple example of my issue with a simple map thumbnail that illustrates the problem visually along with the pertinent .json tomorrow.

Thank you for your generous offer!
Click to expand...

sure, like nadeox said it could just be something as simple as a missing comma but yeah I'll check it out and see if I can figure it out.

Forums

Mods

What do new mappers think of the information available?

Average Person
Expand Collapse

Aboroath
Expand Collapse

Nadeox1
Expand Collapse

Spinning Cube
BeamNG Team

Average Person
Expand Collapse

Useful Searches

What do new mappers think of the information available?

Average Person Expand Collapse

Aboroath Expand Collapse

Nadeox1 Expand Collapse Spinning Cube BeamNG Team

Average Person Expand Collapse

Average Person
Expand Collapse

Aboroath
Expand Collapse

Nadeox1
Expand Collapse

Spinning Cube
BeamNG Team

Average Person
Expand Collapse