Any idea how to add the New User Optional Fields to the Account Menu, so they can be editable by users?
I'm able to display them in the menu (e.g. Pipe + U1) but not make them editable like the rest of the fields. I did find a reference on the wiki that look like it should be possible using (GE) with data: 34, but doesn't appear
to work.

One hack would be to rename one of the New User Questions I'm not
using, but feels like a hack....

--- Mystic BBS v1.12 A46 2020/03/29 (Linux/64)
* Origin: Card & Claw BBS (21:4/158)

On 03 Apr 2020 at 11:50p, Alpha pondered and said...

Any idea how to add the New User Optional Fields to the Account Menu, so they can be editable by users?
I'm able to display them in the menu (e.g. Pipe + U1) but not make them editable like the rest of the fields. I did find a reference on the wiki that look like it should be possible using (GE) with data: 34, but
doesn't appear to work.

Hmm

Well there currently three optional fields (there are provision for 10 in
the optional data section for each user account, but g00r00 seems to have allowed only three to be configured at this point).

I'll see what I can dig up about them but with all the backend changes James has been doing in recent times what I might dig up could have been
superseded by changes to data structures. It's just a guess on my part.

--- Mystic BBS v1.12 A46 2020/03/26 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

I'll see what I can dig up about them but with all the backend changes James has been doing in recent times what I might dig up could have been superseded by changes to data structures. It's just a guess on my part.

Thanks, Avon. Appreciate anything you can dig up!!

--- Mystic BBS v1.12 A46 2020/03/29 (Linux/64)
* Origin: Card & Claw BBS (21:4/158)

Well there currently three optional fields (there are provision for 10 in the optional data section for each user account, but g00r00 seems to have allowed only three to be configured at this point).

I'll see what I can dig up about them but with all the backend changes James has been doing in recent times what I might dig up could have been superseded by changes to data structures. It's just a guess on my part.

FYI - as a workaround in case anyone runs up against this, I ended up changing prompt #441 (User note)... That field *is* editable by users when included
in the Account Menu:

Display Text: BGG Username -> |+U+I
(GE) Edit User Setting
Data: 23

Bingo! Works as well as the optional fields would work.

BUT the next thing I need to learn is how to use MPY(?) to access that record in order to include it as a variable for use in a python API call. If anyone knows how to do that (accessing the record, not the API call) let me know!
I've been reading XQTR's MPL tutorial as well...

--- Mystic BBS v1.12 A46 2020/03/29 (Linux/64)
* Origin: Card & Claw BBS (21:4/158)

BUT the next thing I need to learn is how to use MPY(?) to access that record in order to include it as a variable for use in a python API
call. If anyone knows how to do that (accessing the record, not the API call) let me know! I've been reading XQTR's MPL tutorial as well...

Is it in the records.112 or whatever the file is called? Can you find it in there and use an example of mpl or mpy which leverage other data records and basically figure it out?

--- Mystic BBS v1.12 A46 2020/03/18 (Linux/64)
* Origin: monterey bbs (21:1/168)

Is it in the records.112 or whatever the file is called? Can you find it in there and use an example of mpl or mpy which leverage other data records and basically figure it out?

You're right -- I think with a combo of the records file in /docs and the MPL/MPY examples that come installed with Mystic the basics are all there.
Just need to dive deeper.

--- Mystic BBS v1.12 A46 2020/03/29 (Linux/64)
* Origin: Card & Claw BBS (21:4/158)