Parse Error

[tojimaru]

I type this in my admin.dat file

[level]
level   = 5
name  = Member
flags   = a1d3e4g6h7i9k0mpCDGRHUP

I do !readconfig and I get

!readconfig: [level] parse error near a1d3e4g6h7i9k0mpCDGRHUP on line 5386

Help please?

[mooseberry]

flags

[David]

You probably have a flag not supported by your QVM.
Read its docs to see what it supports.

[tojimaru]

All those flags support the QVM, because I did !help (name of command)  and got those flags.

[Undeference]

Parse errors occur with malformed files. What was pasted looks well-formed, but is that exactly what is in the admin.dat (note that spaces can be important), and is that the exact message?

If those are exact copies, then you may have found a bug. If you want to help the bug get fixed, you should send a test case along with any other relevant information to the appropriate channels. As it is, the closest you have come to mentioning the qvm you use is "the QVM".

FYI, using:
admin.dat in its entirety (which is a direct c+p from the initial post)

Code Select Expand

[level]
level   = 5
name  = Member
flags   = a1d3e4g6h7i9k0mpCDGRHUP
I get

Code Select Expand

]!readconfig
!readconfig: loaded 1 levels, 0 admins, 0 bans, 0 commands


[tojimaru]

The game qvm that I use is P-g-qvm 1.5.2. Yes, that's exactly what I typed in the admin.dat and yes, that is the exact message I get.

[David]

does the admin.dat care about line ends?
Also, test it with TJW's QVm before sending a bug.  If it only happens on the PG one then send the bug to the pgqvm people.  (Or get a better QVM, lak's is good and has less bugs)

[Paradox]

"they arent bugs! they are unintended features!"

[tojimaru]

Well, I tried erasing all the admin things and doing them all over again and it worked this time. Thanks for all your help.

[bob]

!readconfig: [level] parse error near a1d3e4g6h7i9k0mpCDGRHUP on line 5386

This is what I find interesting.

That's probably why erasing all of your junk you had in that file worked.

[Undeference]

!readconfig: [level] parse error near a1d3e4g6h7i9k0mpCDGRHUP on line 5386

This is what I find interesting.

That's probably why erasing all of your junk you had in that file worked.

That's an entirely separate, totally harmless, and completely unrelated bug.