Putting a comment after an int in prj.conf causes an error

RE: Putting a comment after an int in prj.conf causes an error

Seraphina — Sat, 17 Jan 2026 04:57:48 GMT

In Geometry Dash, every click matters as you guide a cube through spikes, traps, and moving obstacles with precise timing and sharp focus.

RE: Putting a comment after an int in prj.conf causes an error

ubiquitybonnet — Wed, 17 Sep 2025 04:36:05 GMT

I agree that this is not really a bug, but rather a limitation of the parser. The solution of putting comments on different lines or avoiding extra whitespace is certainly reasonable and practical. However, a parser that can detect and provide more specific error messages would certainly make geometry dash lite easier for new users to work with, instead of having to figure it out themselves.

RE: Putting a comment after an int in prj.conf causes an error

otiscavin — Tue, 16 Sep 2025 03:20:03 GMT

Zephyr’s parser sometimes misreads inline comments after integer assignments if there’s no spacing or if the parser doesn’t expect extra tokens.

Sprunki

RE: Putting a comment after an int in prj.conf causes an error

Seraphina — Thu, 12 Jun 2025 06:41:41 GMT

To make the error codes easier to work with, I suppose it would be preferable if the parser searched for this problem. As far as I know, there are no plans to address this. Baseball Bros IO

RE: Putting a comment after an int in prj.conf causes an error

Elfving — Fri, 02 May 2025 12:27:01 GMT

Hi,

Yes, we are aware of this being the case. I guess everything after the equals sign is considered a part of the value, unless you explicitly end the value using a final quotation mark. Another thing that would separate KConfig from what you would eg. expect from C, is that a using spaces between the equals sign can be an issue as well.

But I wouldn't think of any of these as a bug per se - it is how to parser works. It has some limitations but that is typically considered fine. You can eg. add the comment on a different line, and don't need the spaces.

I guess it would be better if the parser looked for this issue, to make the error codes easier to work with. I haven't heard of any plans to fix this.

Regards,

Elfving