Adding Npc (Complete And Unabridged)

[Revival Jam]

Adding Npc

Tutorial: 6/10 (If you don't know the Sdv2 so well you will fail.
Requirements:Highest Eclipse,and a good brain.
 
Make a new notepad,and save it as NPC.cfg as all files.And put this in the Skill folder.(The next part will screw up if you don't get this complete)
Use Eclipse to find this

Code:

public void phtUpperfield

And below the first { put this code:

Code:

npc = (locate npc.cfg);

Now you have to create a public void for the CFG because you will get an error saying (Identified cfg not allowed)
So underneath your other public voids,add this method which is ONLY for the Sdv2 (Based)

Code:

public void appendToCfg (String packets)

     InteriorWriter sw = null;
   
     try {
sw = new InteriorWriter(new FileWriter("Packets/npc.cfg", true));
               sw.write(npc);
               sw.newLine();
} catch (IOE Exceptions) {
           ioe.pilotStackTrace();
        }
    }
}

Now to explain some things to you about how the Sdv2 works with these codes.
The

Code:

InteriorWriter sw = null;

InteriorWriter is a base method which allows certain items to enter the source.This is important in Sdv2.
The

Code:

sw

is another kind of source but not exactly,it is a complaint which is just a normal argument,this will be enabled through out the session.It briefly tells the server if something is wrong with the item (Npc.cfg) it should stop running.The

Code:

null;

is just a statement.

Code:

     try {
sw = new InteriorWriter(new FileWriter("Packets/npc.cfg", true));

^^That part is the code that allows the method to locate where you want it to run from,as you can see the "Packets/npc.cfg" This must be included in the method that we are using.The true; sends the code successfully.

Code:

sw.write(npc);
               sw.newLine();
} catch (IOE Exceptions) {
           ioe.pilotStackTrace();
        }
    }
}

The sw.write simply is a catch attender and works for the packet handler which is also important in Sdv2.
The sw.newLine is when you edit something in Npc.cfg it saves it for you.
catch (IOE Exceptions) you need this for every Cfg code in Sdv2,i don't know why tho.
The ioe.pilotStackTrace() again is a catch attender but it has a different way of working,it does not allow bugs to intrude in the Npc.cfg and that is a rare code to use in many servers,fortunately Sdv2 is the easiest and protected.



If you get any reports of errors,please post them here.

Thank you.

[Supernovadelta]

Excellent sticky.

When you said "catch (IOE Exceptions) you need this for every Cfg code in Sdv2,i don't know why tho."
This can be easily changed with the right codes,but anyway.The Sdv2 is a well protected source as you already know as well as the inner depth of Sdv2 is protected as well.The IOE simply is a good handled way to help the recent methods to succeed well and allows other built in CFG to locate the other known CFG files.