Subj : Baja argument help
To   : Digital Man
From : DesotoFireflite
Date : Sun Feb 13 2022 04:43 pm

 Re: Baja argument help
 By: Digital Man to DesotoFireflite on Sun Feb 13 2022 12:11 pm

DM> Re: Baja argument help
DM> By: DesotoFireflite to All on Sun Feb 13 2022 01:47 pm

>> But the way I have it, it also takes the other users to the news
>> message base even if there are no new messages, so I'm sure I have my
>> logic screwed up. It's acting like it's not getting to the secont
>> part. Below is the new file, can someone let me know where I went
>> wrong. Thanks in advance.

>> !include sbbsdefs.inc
>> !include file_io.inc
>> !include dir_attr.inc

>> compare_ars LASTON EQUALS 0 OR REST G
>> if_true
>> # If New User or Guest, go to Local News Message Base and Read News...
>> SETSTR "LOCAL"
>> MSG_SET_GROUP
>> SETSTR "NEWS"
>> MSG_SET_AREA
>> MSG_READ
>> if_false
>> # All other users, go to Local message Base, check for new messages In
>> News, # and show New Messages and if no New Messages exist, do
>> nothing, and exit. SETSTR "LOCAL"
>> MSG_SET_GROUP
>> SETSTR "NEWS"
>> MSG_SET_AREA
>> MSG_NEW_SCAN_SUB
>> end_if

DM> Replace that "if_false" with "else".

Still not working for the regular users, takes them right to the message base. It's like it's not seeing the second part, and giving everyone the first part.
see below, I changed it as you suggested.

!include sbbsdefs.inc
!include file_io.inc
!include dir_attr.inc

compare_ars LASTON EQUALS 0 OR REST G
if_true
# If New User or Guest, go to Local Message Base and Read News...
   SETSTR "LOCAL"
   MSG_SET_GROUP
   SETSTR "NEWS"
   MSG_SET_AREA
   MSG_READ
else
# All other users, go to Local message Base, check for new messages In News, # and show New Messages and if no New Messages exist, do nothing, and exit.
   SETSTR "LOCAL"
   MSG_SET_GROUP
   SETSTR "NEWS"
   MSG_SET_AREA
   MSG_NEW_SCAN_SUB
end_if

I can't understand it, I've worked with Baja before, and I thought I undersood it. I'm figuring with a new user, the last on would be 0(zero), and the Guest would be a restriction of "G", hence "compare_ars LASTON EQUALS 0 OR REST G", so as a regular user with no restrictions, and laston field populated with a date, it should be false, and go to else, the second half, but it's acting like it never sees the second half with regular users, but treats them like a new user or guest. I also tried "compare_ars LASTON=0 OR REST G" and got the same results. My logic must be flawed. It may be the LASTON causing the issue, but I don't know another way of determining a new user with ars or any other method.




SysOp: C.G. Learn, AKA: DesotoFireflite
Valhalla Home Services! - (Synchronet) - bbs.valhallabbs.com
Valhalla II! - (GAP) - bbs.valhallabbs.com:24
Valhalla III! - (RemoteAccess) - bbs.valhallabbs.com:5023
Valhalla IIII! - (Dungeons & Dragons BBS) - bbs.valhallabbs.com:26
Valhalla Home Services Web! - http://bbs.valhallabbs.com
A Gamers Paradise - Over 150 Registered Online Game Doors!
Home Of Odin's Maze Game Server!

--- CAT (n.), Furry keyboard cover.
� Synchronet � Valhalla Home Services � USA � http://valhalla.synchro.net