ID:278246
 
//THIS IS SPECIFICALLY FOR BEGINNER CODERS,OTHERS ARE WELCOME//
This is an example quiz i made, it will show if your actually reading the DM or not.I will make more harder quizzes if people find it useful.

http://www02.quizyourfriends.com/ take-quiz.php?id=0911281508101677&a=1&&
Problems you have:

Question 4: He wants to make an object invisible, but the only answers listed are for making verbs invisible.

Question 5: Worded poorly. I can make a /Win object, set its parent type to /obj, and display it to the user. Also, I can make descendants of /atom, which will also be displayed to the players.

In response to Jeff8500
Also for number 4, his answers are screwy anyways. As defined by DM:

visibility setting (verb)
See:
invisibility setting (verb)
The function of this variable has been replaced by invisibility, which provides a full range of settings.

So using invisibility could have been just as right.
In response to Jeff8500
Jeff8500 wrote:

Question 5: Worded poorly. I can make a /Win object, set its parent type to /obj, and display it to the user. Also, I can make descendants of /atom, which will also be displayed to the players.
The answer to that question is clearly stated in the DM, as it states:

There are four basic object types. Each has its own special properties, as well as those that they all share. The basic objects are mob, obj, turf, and area. There are other objects as well, but these four are the ones which are visible to players. We call them atomic objects.


In response to Tales Number TwO
Ah, that's in the DM guide? I guess that's an oversimplification for beginners.
In response to Radical Designs
Radical Designs wrote:
So using invisibility could have been just as right.

invisibility is right, visibility is wrong. visibility got replaced by invisibility. I missed that as well since he put it incorrectly as set visibility = 0.
In response to Jeff8500
Hmm? Nothing is oversimplified in that bit, and it's entirely correct. Well, except that there is also another object type that can be used to represent and display graphics, the non-atom (but psuedo-atom) /image type. (But that one probably wasn't there when the Guide was written anyway.)

I can make a /Win object, set its parent type to /obj, and display it to the user.

How does that contradict that excerpt? You should know how this works already.
There's nothing special here, you're just displaying an atom, an obj, to a player (so it falls under the definition of atoms being displayable). It just happens to have its path named as "/Win", but it's still an obj nonetheless; the only thing accomplished by setting parent_type is altering what node the object's defined on, i.e. changing the path name of the object, and being a change to a name, it's a purely cosmetic change. If I define /mob/car/X and set its parent_type to /obj/vehicle, it just so happens to be a vehicle obj that has the path of /mob/car/X, although it has nothing to do with /mob.
In response to Kaioken
Well, technically it's not a /obj, but it does inherit from it. Regardless, my subtype of /atom, or /atom/movable/ argument still stands.