DoTA

I have finally done some work on v0.7. Yeah it has been quite a while since I did anything substantial to the Launcher .

Currently I'm working on implementation of "real" Projects and Mods. Mainly I want to move all of my projects "brains" out of the program into the projects themselves and "teach" Launcher how to use that. This will allow you to edit the process of patching with my projects. I also want to add the ability to change project used in simple patching to any other suitable project. Along with that I might also finalize Project/Mods auto-updates.
All those things combined together will finally allow all interested BDO patch creators to redistribute their patch easier and for everyone who uses that patch to update it without waiting the update from patch creator.

I'm currently stuck at the way of saving project info, here is what it looks like now:

Now you're like
Don't worry I'll explain it all when I'll be done with it.

Originally I wanted to make it as human-readable as I can, and the KAMI JP project was just like that^ for quite a while already. On top of that I don't think that I'll add the possibility to create/edit Projects/Mods from the program itself for a very long time after the release of this version, as that will take a lot of time.

Now the problem is in this particular line (and similar ones):

So basically this line says - as a first step after getting everything ready - merge RAW languagedata with Project's languagedata, save the result in M1 (for a later use). The thing is that there also should be a place for actions (after JP1), and in theory there could be a lot of those, basically all planned features related to regex and other automatic text editing/google translation, etc. will go there, so the lines will end up redunculously long. This is also not the best thing from programming standpoint.
There is a workaround with this "style" (to create a lot of entries for each action, like for example 1_1, 1_2, 1_3...), but this will get clunky very fast + not the best thing from programming standpoint.
Of course there is a way to avoid all of that with more nested structure, similar to what I use in scheme, e.g. here is the piece of it:

The thing is, that it might not look like hard to edit (especially when it is as repetitive and simple as this scheme), but it is a lot less human-readable than the first one. No one will care when it will be editable from the program itself, but as I said - it won't be soon.

For now I'm the only one who's using projects, so I don't really mind to change it. If you'll happen to have some better idea then let me know, and I'll think about a better way myself, I just don't want to change it when(if) it will be used by quite a few patch creators.

Maybe use the first way for everything but the steps, for which use the second way?

Margo wrote:Maybe use the first way for everything but the steps, for which use the second way?

It is possible, but it will be even more confusing for the average Joe and will be more complicated than the choice of either of 2, so no.

How is it going?

Magano wrote:How is it going?

Almost haven't done anything since the first post in this thread. No ETA.

Just a small update on how things are going. Basically I've spent a couple of hours on v0.7 through the course of this week. The main work is done, now before the release I need to:
1) Replace existing simple patching code with the one that will use standardized project (easy/time-consuming).
2) Add the ability to select the used projects (easy/might be time consuming, depending on the way that I'll implement it firstly, I might go for the simple way at first and just change that later).
3) Add few things to advanced patching, so that it won't fall behind the functionality of new simple patching

This update will introduce fully featured projects only, mods will be just as they are now. I'm definitely not going to add auto-updates in this version, a lot of time has passed without any updates already, so maybe with the next version. There won't be any simple way to create projects for the nearest future, you will need to take my projects as an example, I'll also try to explain how, where, and what you can do sometime after the update will go live. That's probably it for now, I'll keep you updated on the progress.

I actually decided to merge all KAMI projects into 1, since it's one anyway. Now any project will be able to support multiple clients. Due to this change and more additions, that were not mentioned in this thread (like fonts), I decided that the next version will be v0.7, which doesn't mean a lot to you, but if you'll keep using v0.6x then be ready to adapt new Projects manually (it will be easy), I'll post more info on how and what after the actual release.

KAMIKADzE wrote:I actually decided to merge all KAMI projects into 1, since it's one anyway. Now any project will be able to support multiple clients. Due to this change and more additions, that were not mentioned in this thread (like fonts), I decided that the next version will be v0.7, which doesn't mean a lot to you, but if you'll keep using v0.6x then be ready to adapt new Projects manually (it will be easy), I'll post more info on how and what after the actual release.

You say that you will add fonts - do you mean you will add injector?

Magano wrote:

KAMIKADzE wrote:I actually decided to merge all KAMI projects into 1, since it's one anyway. Now any project will be able to support multiple clients. Due to this change and more additions, that were not mentioned in this thread (like fonts), I decided that the next version will be v0.7, which doesn't mean a lot to you, but if you'll keep using v0.6x then be ready to adapt new Projects manually (it will be easy), I'll post more info on how and what after the actual release.

You say that you will add fonts - do you mean you will add injector?

I guess you mean direct injection of fonts into the client? If so - then no, not with this version. Font can be changed without modifying game files (at least with JP client), I've just added that as a "feature" for those that can't do it manually. That said, since KR client is now "very picky" and don't want to "eat patches", I'll probably add injection with the next version just after this one, so if you need it for whatever reason stay tuned, but it would be great if you could tell me for what do you need it (if for font injection - then in which version it is required?).

KAMIKADzE wrote:

Magano wrote:

KAMIKADzE wrote:I actually decided to merge all KAMI projects into 1, since it's one anyway. Now any project will be able to support multiple clients. Due to this change and more additions, that were not mentioned in this thread (like fonts), I decided that the next version will be v0.7, which doesn't mean a lot to you, but if you'll keep using v0.6x then be ready to adapt new Projects manually (it will be easy), I'll post more info on how and what after the actual release.

You say that you will add fonts - do you mean you will add injector?

I guess you mean direct injection of fonts into the client? If so - then no, not with this version. Font can be changed without modifying game files (at least with JP client), I've just added that as a "feature" for those that can't do it manually. That said, since KR client is now "very picky" and don't want to "eat patches", I'll probably add injection with the next version just after this one, so if you need it for whatever reason stay tuned, but it would be great if you could tell me for what do you need it (if for font injection - then in which version it is required?).

For Korean version English patches.