For any ENiG users out there:
I just pushed a change to the 0.0.9-alpha branch that deprecates the 'options' block in menu.hjson entries. Basically, we had 'config' and 'options' & there was no reason to keep them separated. Anything you had in 'options' can simply be moved to 'config'. For now, you will receive a warning in the log and the system will handle it for you, but that will be removed in future versions.

With this, I added *some* more docs on menus. There is a lot to do around this area. I'm especially intersted in hearing from anyone who has modded their setup & what they found confusing/missing/whatever.

Enjoy!





--- ENiGMA 1/2 v0.0.9-alpha (linux; x64; 8.9.4)
* Origin: Xibalba -+- xibalba.l33t.codes:44510 (21:1/121)

this area. I'm especially intersted in hearing from anyone who has modded their setup & what they found confusing/missing/whatever.

Thank you for all the work you do with ENiGMA 1/2. I really enjoy it. If I come across some theming/mod stuff that is confusing, I will pass it on.

I do have a problem that has been puzzling me though. I'm pretty sure it has something to do with encoding/terminal emulation. I've been trying to emulate some things I've seen on Mystic boards, using python scripts and bash. They are
being spawned by the abracadabra.js door module. Everything looks awesome sauce with the VTX client, but if I use NetRunner or MagiTerm, it looks like a transporter accident. Not just misaligned, it looks like it doesn't have the right character set.

The best I've been able to do is convert the output with something like: iconv -f cp437 -t ms-ansi. It looks OK then, but then it is monochrome. But only in MagiTerm and NetRunner. Still looks fine with VTX.

Any ideas? Is this a Morty mind blower?

fC








--- ENiGMA 1/2 v0.0.9-alpha (linux; x64; 10.8.0)
* Origin: PlaneT Afr0 ~ https://cetialphafive.com/planet_afr0 (21:4/114)

On 08/05/18, fC pondered and said...

Thank you for all the work you do with ENiGMA 1/2. I really enjoy it.
If I come across some theming/mod stuff that is confusing, I will pass
it on.

Hey just a quick hello and welcome to fsxNet - sorry I have yet to hurry up
and update a nodelist etc.. will do this tonight..

..and I agree with you re Enigma1/2 Nu does some amazing stuff!

--- Mystic BBS v1.12 A39 2018/04/21 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

I do have a problem that has been puzzling me though. I'm pretty sure it has something to do with encoding/terminal emulation. I've been trying to emulate some things I've seen on Mystic boards, using python scripts and bash. They are being spawned by the abracadabra.js door module. Everything looks awesome sauce with the VTX client, but if I use NetRunner or MagiTerm, it looks like a transporter accident. Not just misaligned, it looks like it doesn't have the right character set.

Again, very glad you're liking enig so far. It's not for uh... the faint at heart =p

As for your issue: You can set the 'encoding' member in your particular door's config block:
someDoor: {
desc: A Door, duh.
module: abracadabra
config: {
//...the usual..
encoding: cp437
}
}

Give that a whirl. 'encoding' can be whatever it needs to encode *from*. ENiG should then re-encode to whatever your client's term is set to/etc.

...and I'll try to document this a little better (see: "at all")



--- ENiGMA 1/2 v0.0.9-alpha (linux; x64; 8.9.4)
* Origin: Xibalba -+- xibalba.l33t.codes:44510 (21:1/121)