Login
User Name:

Password:



Register
Forgot your password?
Vote for Us!
tintin++ ogg sound player script for linux
Author: Robert Smith
Submitted by: Vladaar
6Dragons ogg Soundpack
Author: Vladaar
Submitted by: Vladaar
6Dragons 4.4
Author: Vladaar
Submitted by: Vladaar
LoP 1.46
Author: Remcon
Submitted by: Remcon
LOP 1.45
Author: Remcon
Submitted by: Remcon
Users Online
CommonCrawl, DotBot, Yandex, joeyfogas

Members: 1
Guests: 7
Stats
Files
Topics
Posts
Members
Newest Member
481
3,735
19,368
618
Micheal64X
Today's Birthdays
There are no member birthdays today.
Related Links
» SmaugMuds.org » Codebases » AFKMud Support & Development » Shop Bug
Forum Rules | Mark all | Recent Posts

Shop Bug
< Newer Topic :: Older Topic > They won't open!

Pages:<< prev 1 next >>
Post is unread #1 Jun 12, 2003, 2:17 pm
Go to the top of the page
Go to the bottom of the page

MadArtist21

GroupMembers
Posts4
JoinedJun 12, 2003

Firstly, hello, I'm MadArtist and I'm using AFKMUD to test my rudimentary coding skills without blowing up someone else's server .

Secondly, I have a major bug in my shops/calendar. I haven't made any adjustments to the two .c files, so here goes-- Basically, whenever I create a shop and give the keeper items as usual and then type list to test it, the keeper gives me this message:

'Sorry, come back tomorrow. I close at (x)pm.' Where x is the time I have set for the shop to close.

Okay, that's normal. But it also occurs when the shop is supposed to be open!

Can anyone tell me if I a) am making a building mistake, or b) screwed something up despite having reinstalled the code like six times?

Here's a sample shop from the SHOPS command:

Keeper: 21000 Buy: 30 Sell: 20 Open: 5 Close: 20 Buy: 1 15 17 19 43

Help help help the stupid newbie!
       
Post is unread #2 Jun 12, 2003, 3:13 pm
Go to the top of the page
Go to the bottom of the page

Samson
Black Hand
GroupAdministrators
Posts3,643
JoinedJan 1, 2002

Test it by setting the shop to open at 0 and close at 28, if you still have problems with that then something is wrong and needs to be looked into. Our shops seem to be working fine.
       
Post is unread #3 Jun 12, 2003, 4:58 pm   Last edited Nov 13, 2005, 1:39 pm by Samson
Go to the top of the page
Go to the bottom of the page

MadArtist21

GroupMembers
Posts4
JoinedJun 12, 2003

Okay, this is what is going on as far as I can surmise:
The game runs perfectly fine right up until 14 o'clock PM. After that hour, it resets to 1 o'clock PM and doesn't change to AM. The days do not change and neither does the month. There's something wrong with calendar.c, but I don't know what.
Maybe it's something with this string?

ch_printf( ch, "It is %d o'clock %s, Day of %s, %d%s day in the Month of %s.\n\r"
 "It is the %s season, in the year %d.\n\r"  
       "The mud started up at:    %s\n\r"
       "The system time (Pacific): %s\n\r",
(time_info.hour % sysdata.hournoon == 0) ? sysdata.hournoon : time_info.hour % sysdata.hournoon,
time_info.hour >= sysdata.hournoon ? "pm" : "am", day_name[(time_info.day) % sysdata.daysperweek], day, suf,
month_name[time_info.month], season_name[time_info.season], time_info.year, str_boot_time, c_time( current_time, -1 ) );


If it helps, I'm currently compiling under cygwin.
       
Post is unread #4 Jun 12, 2003, 10:15 pm
Go to the top of the page
Go to the bottom of the page

Samson
Black Hand
GroupAdministrators
Posts3,643
JoinedJan 1, 2002

14PM is noon, the equivalent of 12PM in normal time. It's normal for 12PM to lead into 1PM, so yes. 14PM leads into 1PM, and the *DAY* won't change until you hit 14AM, as in midnight.
       
Post is unread #5 Jun 13, 2003, 1:44 pm
Go to the top of the page
Go to the bottom of the page

MadArtist21

GroupMembers
Posts4
JoinedJun 12, 2003

Nope, it just keeps cycling through PM. After it goes to 14 PM for the second time, it returns to 1 PM. There are no sunrise/sunset announcements and no day changes.
       
Post is unread #6 Jun 14, 2003, 5:45 pm
Go to the top of the page
Go to the bottom of the page

MadArtist21

GroupMembers
Posts4
JoinedJun 12, 2003

Just updating this in case anyone is interested in how I managed to screw up things:

I fixed it... turned out it wasn't a problem with the code, but with time.dat. I just switched to a new day and hour, compiled, and now it's just fine.
       
Pages:<< prev 1 next >>