Re: [SWCollect] Greetings

2002-10-08 Thread C.E. Forman

 Good point about (S) (T).  I agree it's redundant.  (T) alone works.  What
 about (C)?  The original reason that we had (C) was for a game that was
 sealed, but had become compressed due to the air getting sucked out of
the
 shrink.  However, the current wording for MobyScale could also use (C) for
any
 crushed box -- sealed or not.  Should (C) be used in place of (S), or
should
 it be used for any crushed box?

Hmm, I must have missed this part of the discussion.  The wording on Jim's
page says C = crushed so that's how I've been using it.



--
This message was sent to you because you are currently subscribed to
the swcollect mailing list.  To unsubscribe, send mail to 
[EMAIL PROTECTED] with a subject of 'unsubscribe swcollect'
Archives are available at: http://www.mail-archive.com/swcollect@oldskool.org/




Re: [SWCollect] Greetings

2002-10-08 Thread C.E. Forman

 I also think NM (S) is still valid.  What if you have a defect on the
shrink
 other than a tear (like writing)?  I wouldn't call it MS.

Ah, good point.  NM (S) could indeed apply if there's a defect on the
wrap, but not the game package.



--
This message was sent to you because you are currently subscribed to
the swcollect mailing list.  To unsubscribe, send mail to 
[EMAIL PROTECTED] with a subject of 'unsubscribe swcollect'
Archives are available at: http://www.mail-archive.com/swcollect@oldskool.org/




Re: [SWCollect] Greetings

2002-10-08 Thread C.E. Forman

 Why was it designed to be flexible so individual collectors could tailor
it
 to individual needs?  I might be mistaken, but wasn't the scale designed
to
 be universal?  Being able to tailor anything universal creates confusion,
 no?

Because different collectors have slightly different needs.  The ratings all
mean the same thing (i.e. they are universal) but how people employ them can
very slightly, as we've seen in this discussion.

 Really? would it be that hard?  What type of datafield(s) are you using
for
 the mobyscale condition?

Enum for the conditions, set for the modifiers.  It's not that it'd be that
hard, it's just that it'd take a lot of time to recode, TEST, etc., time I
don't have at the moment.



--
This message was sent to you because you are currently subscribed to
the swcollect mailing list.  To unsubscribe, send mail to 
[EMAIL PROTECTED] with a subject of 'unsubscribe swcollect'
Archives are available at: http://www.mail-archive.com/swcollect@oldskool.org/




Re: [SWCollect] Greetings

2002-10-08 Thread CcomputerGameCollector

 Because different collectors have slightly different needs.  The ratings
all
 mean the same thing (i.e. they are universal) but how people employ them
can
 very slightly, as we've seen in this discussion.

Yea I understand.  I guess I misinterpreted the reasoning behind inventing
the Mobyscale.  My understanding was that it was created to fill all needs
for classifying games so there would be no need for people to adjust the
scale individually.


- Original Message -
From: C.E. Forman [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, October 08, 2002 8:31 AM
Subject: Re: [SWCollect] Greetings


  Why was it designed to be flexible so individual collectors could tailor
 it
  to individual needs?  I might be mistaken, but wasn't the scale designed
 to
  be universal?  Being able to tailor anything universal creates
confusion,
  no?

 Because different collectors have slightly different needs.  The ratings
all
 mean the same thing (i.e. they are universal) but how people employ them
can
 very slightly, as we've seen in this discussion.

  Really? would it be that hard?  What type of datafield(s) are you using
 for
  the mobyscale condition?

 Enum for the conditions, set for the modifiers.  It's not that it'd be
that
 hard, it's just that it'd take a lot of time to recode, TEST, etc., time I
 don't have at the moment.



 --
 This message was sent to you because you are currently subscribed to
 the swcollect mailing list.  To unsubscribe, send mail to
 [EMAIL PROTECTED] with a subject of 'unsubscribe swcollect'
 Archives are available at:
http://www.mail-archive.com/swcollect@oldskool.org/



--
This message was sent to you because you are currently subscribed to
the swcollect mailing list.  To unsubscribe, send mail to 
[EMAIL PROTECTED] with a subject of 'unsubscribe swcollect'
Archives are available at: http://www.mail-archive.com/swcollect@oldskool.org/




Re: [SWCollect] Greetings

2002-10-08 Thread hughfalk

Well, I'm all for having a standard usage for the scale, which would be how
90% of everyone should use it.  Of course people can deviate, but that is
their choice, and hopefully they would call attention to it and reasons why on
their site.  I think I could conform my collection to any scale, and just put
specifics in the notes.

Jim, you haven't weighed in on any of these discussions yet.  Are you around?

Since, Jim is the keeper of the scale, we won't get very far without his
input.

Hugh

On Tue, 8 Oct 2002 08:52:08 -0400 CcomputerGameCollector
[EMAIL PROTECTED] wrote:

  Because different collectors have slightly
 different needs.  The ratings
 all
  mean the same thing (i.e. they are universal)
 but how people employ them
 can
  very slightly, as we've seen in this
 discussion.
 
 Yea I understand.  I guess I misinterpreted the
 reasoning behind inventing
 the Mobyscale.  My understanding was that it
 was created to fill all needs
 for classifying games so there would be no need
 for people to adjust the
 scale individually.
 
 
 - Original Message -
 From: C.E. Forman 
 To: 
 Sent: Tuesday, October 08, 2002 8:31 AM
 Subject: Re: [SWCollect] Greetings
 
 
   Why was it designed to be flexible so
 individual collectors could tailor
  it
   to individual needs?  I might be mistaken,
 but wasn't the scale designed
  to
   be universal?  Being able to tailor
 anything universal creates
 confusion,
   no?
 
  Because different collectors have slightly
 different needs.  The ratings
 all
  mean the same thing (i.e. they are universal)
 but how people employ them
 can
  very slightly, as we've seen in this
 discussion.
 
   Really? would it be that hard?  What type
 of datafield(s) are you using
  for
   the mobyscale condition?
 
  Enum for the conditions, set for the
 modifiers.  It's not that it'd be
 that
  hard, it's just that it'd take a lot of time
 to recode, TEST, etc., time I
  don't have at the moment.
 
 
 
 
 --
  This message was sent to you because you are
 currently subscribed to
  the swcollect mailing list.  To unsubscribe,
 send mail to
  [EMAIL PROTECTED] with a subject of
 'unsubscribe swcollect'
  Archives are available at:
 http://www.mail-archive.com/swcollect@oldskool.org/
 
 
 
 --
 This message was sent to you because you are
 currently subscribed to
 the swcollect mailing list.  To unsubscribe,
 send mail to 
 [EMAIL PROTECTED] with a subject of
 'unsubscribe swcollect'
 Archives are available at:
 http://www.mail-archive.com/swcollect@oldskool.org/
 
 


--
This message was sent to you because you are currently subscribed to
the swcollect mailing list.  To unsubscribe, send mail to 
[EMAIL PROTECTED] with a subject of 'unsubscribe swcollect'
Archives are available at: http://www.mail-archive.com/swcollect@oldskool.org/