A-Net Online

  1. Forum
  2. Zer0net
  3. 0N-CODE

  • Writing DOOR games...

    From xqtr@911:30210/0 to All on Fri Oct 28 18:52:28 2022
    Which environment do you think, that is most suitable now days to write some DOOR game/app?

    - DOS 16bit with an old door kit, that will run under DOS/DOSEMU etc.
    - DOS/WIN/LINUX 32bit, with a more appropriate DOOR kit, like OpenDOOR, RMDOOR.
    - Native script language for a BBS software.

    Which one, would you prefer?

    .
    :: XQTR :: Another Droid BBS :: andr01d.zapto.org:9999 :: xqtr@gmx.com

    --- Mystic BBS v1.12 A47 2020/11/23 (Raspberry Pi/32)
    * Origin: Another Droid BBS # andr01d.zapto.org:9999 (911:30210/0)
  • From esc@911:1719/0 to xqtr on Fri Oct 28 08:58:52 2022
    - DOS/WIN/LINUX 32bit, with a more appropriate DOOR kit, like OpenDOOR, RMDOOR.

    This is my preference, but that's mainly because I think the future compatibility issues with 16 bit DOS software is a concern...at least it is for me. Running doors natively in linux is how I would do things 100% of the time if possible.

    I also think something like a node or python door library would be neat. No need to deal with compilation, multiple distributed versions of a thing, and it can work in any environment with an appropriate interpreter or engine.

    --- Mystic BBS v1.12 A48 2022/07/11 (Linux/64)
    * Origin: m O N T E R E Y b B S . c O M (911:1719/0)
  • From NuSkooler@911:1801/0 to xqtr on Fri Oct 28 17:56:27 2022

    On Saturday, October 29th xqtr muttered...
    Which one, would you prefer?

    JavaScript, Python, etc. have a number of great terminal libraries. stdio and be done wiht it. I did write a quick door in FPC to compile to 8080 a while back, and have done a couple in Rust which can technically compile to just about anything, but writing a "door" is so much easier than people realize I think. There isn't much special, if anything about it on a modern-ish BBS.



    --
    |08 ■ |12NuSkooler |06// |12Xibalba |08- |07"|06The place of fear|07"
    |08 ■ |03xibalba|08.|03l33t|08.|03codes |08(|0344510|08/|03telnet|08, |0344511|08/|03ssh|08)
    |08 ■ |03ENiGMA 1/2 WHQ |08| |03Phenom |08| |0367 |08| |03iMPURE |08| |03ACiDic
    --- ENiGMA 1/2 v0.0.13-beta (linux; x64; 16.16.0)
    * Origin: Xibalba -+- xibalba.l33t.codes:44510 (911:1801/0)
  • From esc@911:1719/0 to NuSkooler on Sun Oct 30 00:37:06 2022
    stdio and be done wiht it. I did write a quick door in FPC to compile to 8080 a while back, and have done a couple in Rust which can technically compile to just about anything, but writing a "door" is so much easier

    Wait wait hold on a sec. You can't just tease us with this information. We need to play with these. Where the hell are they. hehe

    --- Mystic BBS v1.12 A48 2022/07/11 (Linux/64)
    * Origin: m O N T E R E Y b B S . c O M (911:1719/0)
  • From jack phlash@911:1423/0 to xqtr on Sun Oct 30 15:56:27 2022
    on 28 Oct 2022, xqtr said...

    - DOS 16bit with an old door kit, that will run under DOS/DOSEMU etc.
    - DOS/WIN/LINUX 32bit, with a more appropriate DOOR kit, like OpenDOOR, RMDOOR.

    These two. It shouldn't surprise you that this is my choice since this is how I released my last two doors. It gives people running supported modern OSes the ability to run native 32bit versions while also giving retro enthusiasts and weirdos running alternate OSes and/or BBS software the flexibility to run the 16bit version in one way or another.

    (Although, in my case, I really need to port my doors to Linux one of these days instead of *just* win32 and dos16...)

    If I *only* wanted to support modern BBS software, then I might go with the a modern scripting language (but NOT a BBS proprietary one) since it's generally so much easier to create doors without needing to worry about comms, and modern languages tend to have vastly superior string support among other benefits.

    |08j |15A C K |08p |15H L A S H |08!

    --- Mystic BBS v1.12 A47 2021/12/25 (Windows/32)
    * Origin: d i s t o r t i o n // d1st.org (911:1423/0)
  • From Exodus@911:1818/0 to xqtr on Mon Oct 31 17:20:25 2022
    Which environment do you think, that is most suitable now days to write some DOOR game/app?

    - DOS 16bit with an old door kit, that will run under DOS/DOSEMU etc.
    - DOS/WIN/LINUX 32bit, with a more appropriate DOOR kit, like OpenDOOR, RMDOOR.
    - Native script language for a BBS software.

    I still use DDPLUS ...

    --- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
    * Origin: --[!dreamland BBS bbs.dreamlandbbs.org (911:1818/0)
  • From xqtr@911:30210/0 to NuSkooler on Tue Nov 1 15:07:53 2022
    |16JavaScript, Python, etc. have a number of great terminal libraries. std |16be done wiht it. I did write a quick door in FPC to compile to 8080 a w |16back, and have done a couple in Rust which can technically compile to j |16about anything, but writing a "door" is so much easier than people real |16think. There isn't much special, if anything about it on a modern-ish B

    As Esc said... we need more information :)

    The app you made for the 8080 was in DOS? Can FPC do also CP/M? Rust has a
    DOOR kit? or just uses stdio? and do you mean in linux only? how about windows?

    .
    :: XQTR :: Another Droid BBS :: andr01d.zapto.org:9999 :: xqtr@gmx.com

    --- Mystic BBS v1.12 A47 2020/11/23 (Raspberry Pi/32)
    * Origin: Another Droid BBS # andr01d.zapto.org:9999 (911:30210/0)
  • From NuSkooler@911:1801/0 to xqtr on Wed Nov 2 10:02:57 2022

    On Tuesday, November 1st xqtr said...
    As Esc said... we need more information :)
    The app you made for the 8080 was in DOS? Can FPC do also CP/M? Rust has a DOOR kit? or just uses stdio? and do you mean in linux only? how about windows?

    Haha!

    So the "door" I made in 8080 as called "slowmo". It's released under ACiDiC -- it was written in FPC, which has a cross compiler ability. Was a bit of a pain, but worked!

    Bivrost! https://github.com/NuSkooler/bivrost/ is one of the quick projects in Rust. Rust can very very easily cross compile to all sorts of platforms. People have even generated COM files with it (that, I have not tried)

    I just use stdio for doors. I see no reason to do otherwise for Mystic/Sync/Enig/Talisman/whatever. For older DOS/whatever software, it's of course much more limited. No need for a 'door' kit, when you just use a terminal kit. You'll need one that supports disabling features that BBS terminals generally do not support such as CPR or scroll regions, but other than that, "anything" works.

    I'm currently using TerminalKit to develop a terminal RPG/door in JS. For Rust, there are things like https://github.com/redox-os/termion but I have not yet tried them.





    --
    |08 ■ |12NuSkooler |06// |12Xibalba |08- |07"|06The place of fear|07"
    |08 ■ |03xibalba|08.|03l33t|08.|03codes |08(|0344510|08/|03telnet|08, |0344511|08/|03ssh|08)
    |08 ■ |03ENiGMA 1/2 WHQ |08| |03Phenom |08| |0367 |08| |03iMPURE |08| |03ACiDic
    --- ENiGMA 1/2 v0.0.13-beta (linux; x64; 16.16.0)
    * Origin: Xibalba -+- xibalba.l33t.codes:44510 (911:1801/0)
  • From xqtr@911:30210/0 to NuSkooler on Sun Nov 6 11:50:01 2022
    |16I'm currently using TerminalKit to develop a terminal RPG/door in JS. F |16there are things like https://github.com/redox-os/termion but I have no |16tried them.|07

    Thanx for the info :)

    .
    :: XQTR :: Another Droid BBS :: andr01d.zapto.org:9999 :: xqtr@gmx.com

    --- Mystic BBS v1.12 A47 2020/11/23 (Raspberry Pi/32)
    * Origin: Another Droid BBS # andr01d.zapto.org:9999 (911:30210/0)