After copying over to a complete new set up, I copied over the syncrhonet mines directory in full. My local scores stayed, but the inter-bbs ones were removed. Is there something I missed?
After copying over to a complete new set up, I copied over the syncrhonet mines directory in full. My local scores stayed, but the inter-bbs ones were removed. Is there something I missed?
Inter-BBS Minesweeper scores come from the SYNCDATA message base (on DOVE-Net or FidoNet). Once you have that message base populated (do a rescan on your hub?) you should see inter-bbs scores in Minesweeper again.
Re: Syncrhonet Minesweeper
By: Digital Man to The Lizard Master on Fri Oct 13 2023 12:04 pm
After copying over to a complete new set up, I copied over the syncrhonet mines directory in full. My local scores stayed, but the inter-bbs ones were removed. Is there something I missed?
Inter-BBS Minesweeper scores come from the SYNCDATA message base (on DOVE-Net or FidoNet). Once you have that message base populated (do a rescan on your hub?) you should see inter-bbs scores in Minesweeper again.
Quick dumb question, but what is the dove-net equil of %RESCAN? I've never had to do that before and I googled it and I see people talking about it, but I'm not sure.
Also do I need to set the echo mail age prior to 60 days right? Is there a way to do that just for the synchdata sub or no?
Quick dumb question, but what is the dove-net equil of %RESCAN? I've
never had to do that before and I googled it and I see people talking about it, but I'm not sure.
The easiest way is to just telnet to your QWKnet hub (Vertrauen?) using your QWKnet node account and just reset your scan pointer for that sub-board from the QWK menu. There are ways to do remote control via QWK as well, but not strictly required: https://www.synchro.net/docs/message_section.html#RemoteQWKFunctions
you'd have to log in as the QWK user telnet to VERT and set the last read date for the area iirc
The easiest way is to just telnet to your QWKnet hub (Vertrauen?) using your QWKnet node account and just reset your scan pointer for that sub-board from the QWK menu. There are ways to do remote control via QWK as well, but not strictly required:
Re: Syncrhonet Minesweeper
By: Digital Man to The Lizard Master on Fri Oct 13 2023 01:29 pm
The easiest way is to just telnet to your QWKnet hub (Vertrauen?) using your QWKnet node account and just reset your scan pointer for that sub-board from the QWK menu. There are ways to do remote control via QWK as well, but not strictly required:
I logged in, and changed the start date and all the messages came in (4,700 or so) but Mine Sweeper still only shows local scores for some reason. Anything else I need to do?
Double-check that you have the SYNCDATA sub-board and it too got new messages? Each QWK packet is limited in size (or message count) on Vertrauen, so it may take multiple polls to get *all* the DOVE-Net messages stored on Vertrauen. It's a lot more than 4700 messages.
Re: Syncrhonet Minesweeper
By: Digital Man to The Lizard Master on Sat Oct 14 2023 04:40 pm
Double-check that you have the SYNCDATA sub-board and it too got new messages? Each QWK packet is limited in size (or message count) on Vertrauen, so it may take multiple polls to get *all* the DOVE-Net messages stored on Vertrauen. It's a lot more than 4700 messages.
Ah yeah, the earliest message is Oct. 7th. I'll try and keep working at geting it to repoll. Thanks.
You should have sbbs configured to automatically poll periodically in SCFG->Networks->QWK->Hubs->VERT.
Re: Syncrhonet Minesweeper
By: Digital Man to The Lizard Master on Mon Oct 16 2023 11:49 am
You should have sbbs configured to automatically poll periodically in SCFG->Networks->QWK->Hubs->VERT.
Thank you, all seems well there, plus I can force call outs.
No matter what I put for the reset of the pointers (i.e. date or messages) this is the earliest I can get it May 4, 2023.
Then when I force a call out, it goes back to today's date and stil only has 4700 or so messages going back to October 7th.
https://imgur.com/a/LeUh7D1
That's correct, that's the earliest message I have in SYNCDATA. When I said "more than 4700 messages", I was referring to all of DOVE-Net, not just the SYNCDATA conference.
Re: Syncrhonet Minesweeper
By: Digital Man to The Lizard Master on Mon Oct 16 2023 05:44 pm
That's correct, that's the earliest message I have in SYNCDATA. When I said "more than 4700 messages", I was referring to all of DOVE-Net, not just the SYNCDATA conference.
Ah, okay I have an issue on my end I see now. So all I did was do a fresh install of Synchronet and then copied my minesweeper dir (which was running 2.15).
I just now went in and completed a game and I got:
!JavaScript minesweeper.js line 1330: Error: Unrecognized msgbase code: syncdata
I haven't done anything to the message base settings. Here's a screen shot of my settings:
https://imgur.com/a/PhDiP17
I just went into my old VM and it works fine. I don't know what could possibly be different here between the two?
The internal code of is "DOVE-SYNCDATA" (as seen in that screen shot), not "SYNCDATA". I think the fix will be to update your minesweeper code to the latest. Based on that error message and line number, it appears you have an old version of minesweeper there and the newer version should auto-find the "DOVE-SYNCDATA" sub correctly.
Re: Syncrhonet Minesweeper
By: Digital Man to The Lizard Master on Tue Oct 17 2023 11:00 am
The internal code of is "DOVE-SYNCDATA" (as seen in that screen shot), not "SYNCDATA". I think the fix will be to update your minesweeper code to the latest. Based on that error message and line number, it appears you have an old version of minesweeper there and the newer version should auto-find the "DOVE-SYNCDATA" sub correctly.
I was pretty certain that I had the latest, but I overwrote it with the latest git and I get the same thing.
I also checked to make sure the correct version of syncdata.js was there just in case.
I literally just did a clean install a week ago except copying
that folder over from my old system. And now I've overwritten the .js file with the latest git.
I'm not sure what else to check...thanks!
This is the full dir zipped.
https://we.tl/t-DSkoegnf0j
Winners hasn't been updated since I moved it over, losers does, but I guess it's because it errors out on winner update to the syncdata.
This is the full dir zipped.
https://we.tl/t-DSkoegnf0j
The full dir of what? You shouldn't be sharing your sbbs dir tree, if that's what that is, as it contains secrets of your system.
Winners hasn't been updated since I moved it over, losers does, but I guess it's because it errors out on winner update to the syncdata.
Yup, it seems one or more JS files are not current.
I just tried the following in a fresh install of v3.19 on Windows:
C:\sbbs\exec>jsexec -r load('syncdata.js').find()
...
Result (string): dove-syncdata
I just tried the following in a fresh install of v3.19 on Windows:
C:\sbbs\exec>jsexec -r load('syncdata.js').find()
...
Result (string): dove-syncdata
I upgraded that same stock install to v3.20 and tried the same thing and got the same result.
When you login to this system as a user, do you actually see DOVE-Net message areas?
Re: Syncrhonet Minesweeper
By: Digital Man to The Lizard Master on Tue Oct 17 2023 11:59 pm
I just tried the following in a fresh install of v3.19 on Windows:
C:\sbbs\exec>jsexec -r load('syncdata.js').find()
...
Result (string): dove-syncdata
I upgraded that same stock install to v3.20 and tried the same thing and got the same result.
When you login to this system as a user, do you actually see DOVE-Net message areas?
Hmmm...yeah I'm using it currently. I temporarily took off the security limiter just to make sure the sync-data messages were coming through and they seem to be.
And I also get this when I execute the command:
Result (string): dove-syncdata
Ahhhhhhhhhhhhhh. Thank you. It is working now. modopts was set to syncdata instead of dove-syncdata. I had copied and pasted this from the readme.txt when I was setting it up and completely forgot (apologies). I submitted a pull request to update that.Hmmm...yeah I'm using it currently. I temporarily took off the security limiter just to make sure the sync-data messages were coming through and they seem to be.
And I also get this when I execute the command:
Result (string): dove-syncdata
That looks correct.
Do you have a [minesweeper] section in your ctrl/modopts.ini file by chance?
Ahhhhhhhhhhhhhh. Thank you. It is working now. modopts was set to syncdata instead of dove-syncdata. I had copied and pasted this from the readme.txt when I was setting it up and completely forgot (apologies). I submitted a pull request to update that.
Submitted a pull request where?
Maybe you mean "pull" not "pull request" https://docs.github.com/en/pull-req uests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-p ull-requests/about-pull-requests
Re: Syncrhonet Minesweeper
By: Digital Man to The Lizard Master on Wed Oct 18 2023 01:15 pm
Submitted a pull request where?
Maybe you mean "pull" not "pull request" https://docs.github.com/en/pull-req uests/collaborating-with-pull-request s/proposing-changes-to-your-work-with-p ull-requests/about-pull-requests
I was on the main GIT not gitlab and I took that one down. I went to gitlab and I added it there, but if I did something wrong or whatever I'll stick to just submitting ticket requests!
Submitted a pull request where?
Maybe you mean "pull" not "pull request" https://docs.github.com/en/pull-req uests/collaborating-with-pull-request s/proposing-changes-to-your-work-with-p ull-requests/about-pull-requests
I was on the main GIT not gitlab and I took that one down. I went to gitlab and I added it there, but if I did something wrong or whatever I'll stick to just submitting ticket requests!
I'm not following. The "main GIT" for Synchronet is gitlab.synchro.net. You went to gitlab and added *what* there?
syncdata line in the ini file for readme.txt wasn't a big deal I'd submit a change. I went to https://github.com/SynchronetBBS/sbbs and it said it requried a pull request so I did that and it was sitting up there for approval, but I took it down when I found the gitlab. I went to gitlab and added the line to readme.txt, but I'm assuming it was just on my branch that it created.
Basically I was just trying to change the readme.txt line where it talks about adding [minesweeper] in modopts.ini to say sub = dove-syncdata from sub = syncdata which was causing my issue. I had just copied and pasted it from there.
You want to change the minesweeper/readme.txt to state the default "sub" key value is "dove-syncdata"? It's not, it's "syncdata". We could change the default (in minesweeper.js) from "syncdata" to "dove-syncdata", but since the syncdata.js library automatically finds the correct sub code (so long as it *ends* in "syncdata"), there's really no need to do this. That's the whole point of the syncdata.js library. :-)
If anything should be added to the readme.txt it would probably be a statement like: "don't add anything to your modopts.ini that you don't expressly need".
Re: Syncrhonet Minesweeper
By: Digital Man to The Lizard Master on Thu Oct 19 2023 10:53 am
You want to change the minesweeper/readme.txt to state the default "sub" key value is "dove-syncdata"? It's not, it's "syncdata". We could change the default (in minesweeper.js) from "syncdata" to "dove-syncdata", but since the syncdata.js library automatically finds the correct sub code (so long as it *ends* in "syncdata"), there's really no need to do this. That's the whole point of the syncdata.js library. :-)
If anything should be added to the readme.txt it would probably be a statement like: "don't add anything to your modopts.ini that you don't expressly need".
I get what you are saying. What happened in my case is I hadn't reset the message pointers so it was coming up blank. In trying to fix that I added the entry in modopts.ini, I've removed it and it still works now post doing that.
I doubt anyone will ever have that exact issue, and it was me fumbling through it. That being said it was all default otherwise and if you copy and paste what's in the readme.txt to the modopts.ini file it does not work. So that's what I'd update, but I doubt anyone will ever have that issue anyway.
If you copy and paste it directly you will get the syncdata not found error in minesweeper.js.
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 368 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 87:02:24 |
| Calls: | 7,895 |
| Calls today: | 1 |
| Files: | 12,968 |
| Messages: | 5,792,152 |