Code L2Jxtend **customs Made Simple**

[Elfosass]

So today im coming back hot to the l2j scene with a new idea which i'm gonna extend and develop as the days go by with my friend Anarchy.

 

You might have noticed that there are custom codes and features floating around everywhere but they are messy coded, developed in not efficient ways and often makes us end up with huge patches to add every time.

 

The point of this project is having all the custom features we can get as packaged and configurable as possible while in the same time it supports all the packs and projects requested.

 

Current features:

• Pvp Color system
• Pvp skills reward system
• Pvp items reward system
• VoicedCommand Support (Without affecting acis)
• Vote Reward system for L2Network and L2TopZone
• Classic .online and advanced .online+ command (Can see how many are farming and how many pvp etc)
• Action Listener engine to be used on stuff later.

• Support for the Android Application L2jXtend OnTheGo (Gonna be released by tomorrow morning as technical alpha

• Added support for Hopzone

• Damage multiplier for classes and mobs.

   

   

 

TODO List:

• Ingame json configuration management
• Passcode system
•  

 

Why L2jXtend?

• One file for the most packs in the market.
• Clean and efficient coding.
• "Less is more" design. Minimalistic but still configurable.
• Just one small jar and one small patch.
• JSON support.
• Specific coding model.

 

How it works?

 

Just add the JAR file in the libs and the configs to the config folder.

Add the patch and configure the JSON configuration files.

 

 

What is JSON?

 

So probably a good portion of you might not know what JSON is.

JSON (Pronounced Jason) stands for JavaScript Object Notation and its a lightweight data-interchange format.

It's probably the best way of storing static data such as configurations for l2j because is easy for humans to read and write but also easy for machines to parse and generate.

 

The following is an example of describing a person in JSON:

{
  "firstName": "John",
  "lastName": "Smith",
  "isAlive": true,
  "age": 25,
  "height_cm": 167.6,
  "address": {
    "streetAddress": "21 2nd Street",
    "city": "New York",
    "state": "NY",
    "postalCode": "10021-3100"
  },
  "phoneNumbers": [
    {
      "type": "home",
      "number": "212 555-1234"
    },
    {
      "type": "office",
      "number": "646 555-4567"
    }
  ],
  "children": [],
  "spouse": null
}

Well i know. At first glance you won't understand the syntax but if you break it bit by bit it's readable and easily expandable.

 

Let me use an example from the first feature added to l2jxtend which is the pvpcolor system.

{
	"enabled" : "false",
	"pvpcolorcount":[
	{"count":"100", "color":"00FFFF"},
	{"count":"200", "color":"FF00FF"},
	{"count":"300", "color":"FFFF00"}
	]
}

The code above is the json file you will edit for the pvp color system. as you can see you have a true false boolean first option and then a pvpcolorcount option for the count and color values you are going to use. You can use as many as you want as long as you extend the array.

 

Here is an example with 5 colors.

{
	"enabled" : "false",
	"pvpcolorcount":[
	{"count":"100", "color":"00FFFF"},
	{"count":"200", "color":"FF00FF"},
	{"count":"300", "color":"FFFF00"},
	{"count":"400", "color":"FF0000"},
        {"count":"500", "color":"FFFFFF"},
	{"count":"600", "color":"FF0F00"}
	]
}

Ain't that hard right?

 

 

Why JSON?

 

It is a really thinner version of XML and also a faster one to parse for java to use.

No comments, no lengthy texts and files. Only what you need in a really minimal designed language.

 

 

Download links

1.0: https://mega.co.nz/#!S9USSBgZ!JHre0GMG0LCxWB_JNX14Dt1c2b6DbjnJN_f8GEaet_g

Rev 9: https://mega.co.nz/#!C5MywRib!2foFO6GxJ2P3JZDGHTjTHzd6mi7r8GQ05IbZglcc7lk

Rev 18: https://mega.co.nz/#!60cwEZhT!ZykIEqp1T76RT7B5ZMAVLsWjkVzFni_OBpZJpwIfwMM

Rev 21: https://mega.co.nz/#!isdwHLAb!FBs2AFm9sztGSE1lprp4zyNpvlk89uoWyuVV4sL64iw

Rev 26:  https://mega.co.nz/#!LwtGGCaI!D-kC7j67kzbAdkaNSxaZxUUSxxeLHEjXbEZGDS5BcLw

 

PS: By the end of the day i will update you with the latest version with more features.

 

Please comment with features you want to see in the future in our project.

Edited July 9, 2015 by Elfosass

[ZaNteR]

Is this only for interlude or will work with everything?

[Lioy]

Nice share, i doubt if anybody use it (that's the community).

[Elfosass]

Is this only for interlude or will work with everything?

For now its only for acis and only one feature.

 

 

Nice share, i doubt if anybody use it (that's the community).

If you see my TODO list then you gonna be sure that everyone is going to use it. ;)

[fissban]

because using json when we can write the same things in java and keep the basis of the l2j projects or use alternative language we all know and are accustomed to using as xml

Although the idea is good but it is being used long ago by some programmers do not want to show their source code to sell codes.

but yes, I like the idea.

Edited March 26, 2015 by fissban

[Tessa]

Just to point, YAML is more readable :lol:

enabled: false
    pvpcolorcount:
        count: 100
            color: "00FFFF"
        count: 200
            color: "FF00FF"
        count: 300
            color: "FFFF00"
        count: 400
            color: "FF0000"
        count: 500
            color: "FFFFFF"
        count: 600
            color: "FF0F00"

[Elfosass]

because using json when we can write the same things in java and keep the basis of the l2j projects or use alternative language we all know and are accustomed to using as xml

Although the idea is good but it is being used long ago by some programmers do not want to show their source code to sell codes.

but yes, I like the idea.

I know i used it to to hide code but there is no point on doing that as the code is being easily decompiled. I just wanna have everything organized.

 

 

Just to point, YAML is more readable :lol:

enabled: false
    pvpcolorcount:
        count: 100
            color: "00FFFF"
        count: 200
            color: "FF00FF"
        count: 300
            color: "FFFF00"
        count: 400
            color: "FF0000"
        count: 500
            color: "FFFFFF"
        count: 600
            color: "FF0F00"

Not for big files plus it is most of the times slower than JSON.

[vampir]

Not for big files plus it is most of the times slower than JSON.

I don't know why would you care about speed of loading configuration files since you are loading them only on launching gameserver + reloading.

 

I suggest to use Logging included in the Pack.

 

If you will not create larger engine for holding the data, making tons of maps will be pain in the ass.

[Elfosass]

I don't know why would you care about speed of loading configuration files since you are loading them only on launching gameserver + reloading.

 

I suggest to use Logging included in the Pack.

 

If you will not create larger engine for holding the data, making tons of maps will be pain in the ass.

This logic won't get you somewhere. For the same reason acis should never move from sql to xml.

I prefer going with the flow.

[fissban]

I am interested in the job but rather see him using xml instead of jason.

 

I would like to see the code that "jar" that gone up because without the source code would trust me never work but more so than my confidence to bring something if it so decides.

thx

[vampir]

This logic won't get you somewhere. For the same reason acis should never move from sql to xml.

I prefer going with the flow.

Those are 2 different things. I have got at the moment 768 configs which are loading in 253 milliseconds. If this time would extend 10 times i wouldn't care, as long as it would give me flexibility(like xmls comparing to mysql) or something else. I am not saying JSON isn't good, but that speed of its usage isn't a good argument in here :)

 

 

I am interested in the job but rather see him using xml instead of jason.

 

I would like to see the code that "jar" that gone up because without the source code would trust me never work but more so than my confidence to bring something if it so decides.

thx

You can use decompiler to see the code

Edited March 26, 2015 by vampir

[Elfosass]

Those are 2 different things. I have got at the moment 768 configs which are loading in 253 milliseconds. If this time would extend 10 times i wouldn't care, as long as it would give me flexibility(like xmls comparing to mysql) or something else. I am not saying JSON isn't good, but that speed of its usage isn't a good argument in here :)

Ofc it is and as a programmer all that matters is really milliseconds. The thing is i prefer SQL over XML but i also prefer performance over personal preference so i ended up at this decision.

[vampir]

Ofc it is and as a programmer all that matters is really milliseconds. The thing is i prefer SQL over XML but i also prefer performance over personal preference so i ended up at this decision.

Ok :) I hope this will be big extender someday. Good luck

[Tryskell]

It remembers me "Lelouch" project.

 

The idea is good, but you have to know some methods won't fit between projects (L2J project itself from chronicle to chronicle rename methods). I edit methods names aswell when L2J didn't do it yet.

[Elfosass]

It remembers me "Lelouch" project.

 

The idea is good, but you have to know some methods won't fit between projects (L2J project itself from chronicle to chronicle rename methods). I edit methods names aswell when L2J didn't do it yet.

I know there will be separate patches for the projects themselves and difference packages inside the jar for every pack in the form of mods.acis or mods.l2jsunrise .