Double-Up! v2.0 by Darryl Perry 2014-2018 Double-Up the newer multiBBS version has rarely worked for my BBS. It is setup as right as I can make it and was working originally for a month[SNIP]
do whatever. The error message I see is the one many now see:
This Python has API version 1013, module __mysticerror__ has version 2122974197.
On 13 Apr 2019, bcw142 said the following...
Double-Up! v2.0 by Darryl Perry 2014-2018 Double-Up the newer multiBBS version has rarely worked for my BBS. It setup as right as I can make it and was working originally for a mont[SNIP]
do whatever. The error message I see is the one many now see:
This Python has API version 1013, module __mysticerror__ has version 2122974197.
So after a quick look at things I'm now guessing it's a python 2 to 3 thing, and has happened due to updates. So my guess is we need to change the ibbs.mpy part of Double-Up! to fix the issues between python 2 vs python 3 due to updates in the OS. Check out: https://sebastianraschka.com/Articles/2014_python_2_3_key_diff.html
I suspect ibbs.mpy can be updated to work. I'll be trying to test things to see if I can figure it out. Worse case is trying to reverse the
updates since they're part of the OS.
If you get it to work by fixing the script, then that would be great.
But I suspect that the error is with how mystic incorporates python. If that's the case, then I don't see a possiblilty of fixing it without a change to Mystic itself.
If you want a look at what I mean by duscore.asc being garbled you can look at bcw142.zapto.org (all default ports work) from the main menu X
the /S and the Double-Up! 'garbled' scores are shown. The working scores (duscore.ans) is in the Door menu under T in the full Top scores list I created.
On 15 Apr 2019, Gryphon said the following...
If you get it to work by fixing the script, then that would be great. But I suspect that the error is with how mystic incorporates python. that's the case, then I don't see a possiblilty of fixing it without change to Mystic itself.
I know I have the right version of python now so I know it's not the version. The testpython.mpy script works fine and I believe your script
is sending data out, it the receiving side that isn't working. Also the scores view (L) doesn't work. I think it's the duscore.asc that is
causing it. I've found that duscore.ans works fine and can be viewed
with the GD command followed by a GT with BarCRBarPA to pause it on screen. What the L command does I'm not sure but the duscore.asc is garbled at best on the Pi, where the duscore.ans works fine. I'm going
to look in to trying to get the L command to function first, then start getting the FSXDAT stuff to work after that.
If you want a look at what I mean by duscore.asc being garbled you can look at bcw142.zapto.org (all default ports work) from the main menu X
the /S and the Double-Up! 'garbled' scores are shown. The working scores (duscore.ans) is in the Door menu under T in the full Top scores list I created.
On 20 Apr 2019 &4, bcw142 said the following...
If you want a look at what I mean by duscore.asc being garbled you ca look at bcw142.zapto.org (all default ports work) from the main menu the /S and the Double-Up! 'garbled' scores are shown. The working sco (duscore.ans) is in the Door menu under T in the full Top scores list created.
does that happen every time the game gets played?
Sysop: | echicken |
---|---|
Location: | Toronto, Ontario |
Users: | 2,224 |
Nodes: | 6 (0 / 6) |
Uptime: | 209:30:22 |
Calls: | 14,142 |
Files: | 295 |
Messages: | 551,093 |