Skip to main content ↑ ↓
Topic: Introduction/retirement date (Read 15878 times) previous topic - next topic

Introduction/retirement date

If I set intro date 01/1930, the new object will be available at 00:00 of 01/1930.

If I set retire date 01/1930, the old object will be available until 23:59 of 12/1929 and unavailable from 00:00 of 01/1930.

Am I correct?

Re: Introduction/retirement date

Reply #1 –
yes (if correctly and consistently implemented).
Parsley, sage, rosemary, and maggikraut.

Re: Introduction/retirement date

Reply #2 –
Thank you!

So, if one object simply replaces an older one, the intro date of the former needs to be that of the latter. It makes perfectly sense :)

(my doubt was: should i put intro 01/1930 and retire 12/1929? Better and easier like it is)
 

Re: Introduction/retirement date

Reply #3 –
SInce the month and the years are caluclated together I think 13/1929 and 1/1930 gives also the same ...

Re: Introduction/retirement date

Reply #4 –
Quote from: fabio – on
If I set intro date 01/1930, the new object will be available at 00:00 of 01/1930.

If I set retire date 01/1930, the old object will be available until 23:59 of 12/1929 and unavailable from 00:00 of 01/1930.

Am I correct?
Uhm... err... I don't know what the code says about this, but I guess the answer is no. Both should be 01/1930 00:00, as long as I get replacement messages together for obsolete and new vehicles. I mean, in pak128 there are lots of vehicles that replace other vehicles in timeline, and I get always the availability message at same time than the obsolete message (that could have changed in newer versions though). Anyway you won't notice as long as it is just one second after, would you? ;D

Edit: About the messages, the trick is -IIRC- they do not always appear in the same order. I'll check it in further games anyway...

Re: Introduction/retirement date

Reply #5 –
These messages are shown on the start of a new month.
Parsley, sage, rosemary, and maggikraut.

Re: Introduction/retirement date

Reply #6 –
@Dwachs: As long as availability/retire dates can be tuned up to month+year, the "available until" and "unavailable from" is a single instant, isn't it? If you use the same retire date for vehicle A and availability date for vehicle B, they will become obsolete (A) and available (B) at same time. Any other configuration would mean a gap of at least one month without any of them (or both) available. Am I right?

PS: Btw, I've completely lost the goal of this thread... are we into a metaphysical discussion? :P

Re: Introduction/retirement date

Reply #7 –
Quote
If you use the same retire date for vehicle A and availability date for vehicle B, they will become obsolete (A) and available (B) at same time. Any other configuration would mean a gap of at least one month without any of them (or both) available. Am I right?

Yes.

And as an answer to your earlier comment: The order of the individuall intro/retire messages is 'random' and has no meaning. All these vehicles become available/obsolete at precisely the same time.
Parsley, sage, rosemary, and maggikraut.

Re: Introduction/retirement date

Reply #8 –
The goal is precisely avoiding gaps in the timeline of new pak128 roads set :)

Re: Introduction/retirement date

Reply #9 –
@Dwachs: thanks for your explanations :)

@fabio: heh, perfect then. Same dates for "item A retire" and "item B intro" will result in no gap and no overlapping between items A and B. Instant change!