Hello. I am a programmer that looking for job. If you want to hire me, fix a bug or just make a code for you PM me or reply on this thread. Knowledge of Java.  Price negotiable. PM me.

Any preview of your work ?
Any trades you 've made in the past ??

Hello. I am a programmer that looking for job. If you want to hire me, fix a bug or just make a code for you PM me or reply on this thread. Knowledge of Java.  Price negotiable. PM me.

To start with, you are 18. You are not a programmer but a wannabe.

Show us your work.

Hello. I am a programmer that looking for job. If you want to hire me, fix a bug or just make a code for you PM me or reply on this thread. Knowledge of Java.  Price negotiable. PM me.

 

A simple question, your navicat's items table contains L2Item or L2ItemInstance?

A simple question, your navicat's items table contains L2Item or L2ItemInstance?

Yeah lets play! :D

 

Why to compile Core you don't need to have scripts.jar in library, but you need to have l2jserver.jar to compile scripts?

Yeah lets play! :D

 

Why to compile Core you don't need to have scripts.jar in library, but you need to have l2jserver.jar to compile scripts?

 

the "programmer" won't answer I guess. If I got it right scripts.jar uses l2jserver imports and not viceversa

Yeah lets play! :D

 

Why to compile Core you don't need to have scripts.jar in library, but you need to have l2jserver.jar to compile scripts?

scripts.jar? you dont compile the datapack scripts. datapack when you run ant does not use java. it doesnt really compile, it just gathers all the files and give a user friendly output in order to add it on the gameserver output. The scripts are compiled apon usage when you run the gameserver via the scriptengine. Datapack uses the other project location in order to get the imports etc, while the scripts are extension of the project, which means that they dont need any jar but just the instruction.

 

PEW

scripts.jar? you dont compile the datapack scripts. datapack when you run ant does not use java. it doesnt really compile, it just gathers all the files and give a user friendly output in order to add it on the gameserver output. The scripts are compiled apon usage when you run the gameserver via the scriptengine. Datapack uses the other project location in order to get the imports etc, while the scripts are extension of the project, which means that they dont need any jar but just the instruction.

 

PEW

Ah, I am compiling it every time so those files are only in scripts.jar.

    <target name="compile" depends="init" description="Compile the source.">
        <javac destdir="${build.classes}" optimize="on" debug="on" source="1.7" target="1.7" nowarn="off" includeantruntime="false" >
            <src path="${src.scripts}" />
            <classpath refid="classpath" />
        </javac>
    </target>

    <target name="jar" depends="compile" description="Create the jar file">
        <jar destfile="${build}/scripts.jar">
            <fileset dir="${build.classes}" >
                <exclude name="**/loginserver/**"/>
                <exclude name="**/commons/**"/>
                <exclude name="**/accountmanager/**"/>
                <exclude name="**/gsregistering/**"/>
            </fileset>
        </jar>
        <copy todir="${build.dist.libs}">
            <fileset dir="${build}">
                <include name="scripts.jar" />
            </fileset>
        </copy>

        <delete dir="${build.classes}" />
    </target>

I forgot that it's working differently in most of the packs :P

Ah, I am compiling it every time so those files are only in scripts.jar.

    <target name="compile" depends="init" description="Compile the source.">
        <javac destdir="${build.classes}" optimize="on" debug="on" source="1.7" target="1.7" nowarn="off" includeantruntime="false" >
            <src path="${src.scripts}" />
            <classpath refid="classpath" />
        </javac>
    </target>

    <target name="jar" depends="compile" description="Create the jar file">
        <jar destfile="${build}/scripts.jar">
            <fileset dir="${build.classes}" >
                <exclude name="**/loginserver/**"/>
                <exclude name="**/commons/**"/>
                <exclude name="**/accountmanager/**"/>
                <exclude name="**/gsregistering/**"/>
            </fileset>
        </jar>
        <copy todir="${build.dist.libs}">
            <fileset dir="${build}">
                <include name="scripts.jar" />
            </fileset>
        </copy>

        <delete dir="${build.classes}" />
    </target>

I forgot that it's working differently in most of the packs :P

yeah indeed your project does compile but any other l2j project till now has no need to compile cuz it uses scriptengine. yours dont. 

i don't really find it efficient if you ask me cuz you nagate the meaning for having the scripts at the point you do.

yeah indeed your project does compile but any other l2j project till now has no need to compile cuz it uses scriptengine. yours dont. 

i don't really find it efficient if you ask me cuz you nagate the meaning for having the scripts at the point you do.

1. When i am making changes in scripts, i don't need to put the files on server machine one by one everytime

2. I can protect jar before giving it to somebody.

3. I always add backdoors

i don't really find it efficient if you ask me cuz you nagate the meaning for having the scripts at the point you do.

 

Compiled, it improves response.

Compiled, it improves response.

 

just load speed by 5-10 seconds

just load speed by 5-10 seconds

 

Bits of byte code dynamically into real, it's a big deal.