General Discussion

[CherryWood]

Do you mean existing or unique item? Cause if unique, with a new icon and stuff, then we need to load items from multiple jsons.

I've simply created a new items_whateveruniquename.xml file in content/db, with icon image patch to gilpack folder and new item appeared in game. Is there something else to do?

[DarkTl]

Nah, not for you, but for Xela. Ideally, such items xmls/jsons should be in the girl's folder, otherwise it will be too difficult to install them.

[Xela]

Nah, not for you, but for Xela. Ideally, such items xmls/jsons should be in the girl's folder, otherwise it will be too difficult to install them.

There is a line for allowing easy modding passed which I'd say: "F@ck it"

This steps over that line. Items can just as easily be coded in Python as loaded from XML. I'd rather show how to do that.

[DarkTl]

Are you telling me it's too difficult to load several items jsons in the game?
We already do it with girls data files.

[Xela]

Are you telling me it's too difficult to load several items jsons in the game?
We already do it with girls data files.

No, what I am saying is that there are:

Items, Traits, Battle/Magic Skills, Say window customization (possibly multiple windows), Advanced stats (overrides), Levels and more. If someone wants to do any of it for girls (later maybe for some random characters or Arena fighters as well), they can do it in start_id label in python, not in a sh!tloads of  xml/json files.

PS: Not mentioning that this way girls from large packs can be processed in bulk as well.

[DarkTl]

How do you propose to problemlessly distribute such changes? Even our Repo won't help.

[Xela]

How do you propose to problemlessly distribute such changes? Even our Repo won't help.

?

[DarkTl]

If two independent modders modify the items.json to add some unique items, that means manual editing for everyone else. And you saw how many problems with installing packs people have even now.

If they both use Repo, their changes will be merged, but everyone else will have to use their packs.

[Xela]

If two independent modders modify the items.json to add some unique items, that means manual editing for everyone else. And you saw how many problems with installing packs people have even now.

If they both use Repo, their changes will be merged, but everyone else will have to use their packs.

I still don't follow? I said advanced modding should be done with python, why are you still talking about json files?

[DarkTl]

That's an example. If two independent peolpe will change something packs-related in the code, we will have the very same problem.

[Xela]

That's an example. If two independent peolpe will change something packs-related in the code, we will have the very same problem.

I will only add mods that do not break anything to the game, what modders do with add-on mods is their business. I cannot see the problem that you describe, maybe I am missing something or you misinterpret how the game code is working...

[DarkTl]

Nope, that's everyone's business. Because everyone will have to modify the code in order to use third party mods.

While it's not a problem if we stick to that "their business" attitude, we might as well use rpa archives for content then 

[Xela]

Nope, that's everyone's business. Because everyone will have to modify the code in order to use third party mods.

Like I've said in previous post, I don't think we understand one another on this topic.

While it's not a problem if we stick to that "their business" attitude, we might as well use rpa archives for content then 

As I've said before, reasons why we shouldn't are far more numerous than reasons why we should.

[DarkTl]

Ok, let's try another approach. How to create an item without using items json?

[Xela]

Ok, let's try another approach. How to create an item without using items json?

I've never tried, but it would look something like this:

Code: [Select]

    item = Item()
    item.id = "id"
    item.icon = "path/imagename.png"
    item.mod = dict(charisma=15, attack=20}

    items[item.id] = item
Can be simplified even further (item would not have be be spelled out every time) but right now the constructor doesn't take any arguments.