Discussion SQL -> XML using template

[Kara]

Greetings, i'm not familiar with the conversion, i would love let's say to move NPC's with their elements, AI, skills into xml using a template i want. 

The question is how you make this happen automatically? Im thinking it's a procedure like, let's say JOIN tables and then you do what?

Thanks a lot

Ps. im about to code a sql-xml generator which will do the work for me using a template ill add and replace the fields after i JOINED them all. 

Edited October 30, 2017 by GamePsychology

[Elfo]

The real question is why you want to do that?

[Kara]

1 hour ago, .Elfocrash said:

The real question is why you want to do that?

Unfortunately i've done it already. Made a 500 line code and convert it using template from sql to xml. 

The reason i want to do this is because i find xml easier to adjust than enter in SQL. In the end i can add more variables such as parameters and no have to create new table in navicat. Why you don't like it? 

 

Kinda the idea.: 

  

	<npc id="%id%" %templateId% level="%level%" type="%type%" name="%name%" title="%title%">
        <race>%race%</race>
        <sex>%sex%</sex>
        <stats str="%str%" con="%con%" dex="%dex%" wit="%wit%" int="%int%" men="%men%" exp="%exp%" sp="%sp%">
            <vitals hp="%hp%" mp="%mp%" hpRegen="%hpRegen%" mpRegen="%mpRegen%" />
            <attack physical="%physical%" magical="%magical%" critical="%critical%" atkSpd="%atkSpd%" mAtkSpd="%mAtkSpd%" range="%range%" aggro="%aggro%" rhand="%rhand%" lhand="%lhand%" enchant="%enchant%"/>
            <defence physical="%defPhysical%" magical="%defMagical%" />
			%attributes%
            <speed>
                <walk speed="%wspeed%" />
                <run speed="%rspeed%" />
            </speed>
        </stats>
        %skills%
        <targetable>%targetable%</targetable>
        <show_name>%show_name%</show_name>
        <dropHerbGroup>%dropHerbGroup%</dropHerbGroup>
        <baseStats>%baseStats%</baseStats>
        %ai%
        <collision>
            <radius normal="%colradius%" />
            <height normal="%colheight%" />
        </collision>
    </npc>

 

Edited October 30, 2017 by GamePsychology

[Elfo]

It is a case by case scenario tbh.

Platforms that don't need to be flexible and try to replicate a playstyle (aCis, Unity, L2jServer) can benefit from XML because there is no need for tables. Values that essentially will never change or they will be changed once.
Platforms that need to be flexible and constantly change and fine tune the game play (any l2j server ever) would benefit from SQL as it is way more flexible, able to do relations between entities easily and flexibly.

I find the sql -> xml change  downgrade personally because of how fluent i am in SQL and what i can achieve with it.
Just a personal opinion here.

Edited October 30, 2017 by .Elfocrash

[Kara]

34 minutes ago, .Elfocrash said:

It is a case by case scenario tbh.

Platforms that don't need to be flexible and try to replicate a playstyle (aCis, Unity, L2jServer) can benefit from XML because there is no need for tables. Values that essentially will never change or they will be changed once.
Platforms that need to be flexible and constantly change and fine tune the game play (any l2j server ever) would benefit from SQL as it is way more flexible, able to do relations between entities easily and flexibly.

I find the sql -> xml change  downgrade personally because of how fluent i am in SQL and what i can achieve with it.
Just a personal opinion here.

Afcourse your opinion is helpful, but still i can't get why you consider this a downgration. SQL is useful when there is connectivity - relation between data. But in case of L2J is very "opposite" situation. Except the droplist which afc ill let in SQL cause i like to be non static and used by admin all other data i guess does not affect the values written in current database such as NPC elementals e.t.c

Edited October 30, 2017 by GamePsychology

[Kara]

18 hours ago, .Elfocrash said:

It is a case by case scenario tbh.

Platforms that don't need to be flexible and try to replicate a playstyle (aCis, Unity, L2jServer) can benefit from XML because there is no need for tables. Values that essentially will never change or they will be changed once.
Platforms that need to be flexible and constantly change and fine tune the game play (any l2j server ever) would benefit from SQL as it is way more flexible, able to do relations between entities easily and flexibly.

I find the sql -> xml change  downgrade personally because of how fluent i am in SQL and what i can achieve with it.
Just a personal opinion here.

You affected me, i made it and the next minute i dropped it back to SQL :/

You ruined my dreams sir 

[SweeTs]

On 30.10.2017 at 4:09 PM, GamePsychology said:

Afcourse

Oh you.. This confirm peoples suspicious, you are Access. Without doubts :D

Edited October 31, 2017 by SweeTs

[Kara]

1 hour ago, SweeTs said:

Oh you.. This confirm peoples suspicious, you are Access. Without doubts :D

Who suspect this and who is Access? 

Edited October 31, 2017 by SweeTs