Weeg 28 (original counter: 131) (21/07/2021)

Also this week I worked on the Memory Viewer/Editor again. Unfortunately, I found out that Microsoft's native lists are not good enough for my purposes. By regularly updating the values from a list (see the gif for this), it starts to flicker. I also managed to stop the flickering, but then the performance was so bad that you had a significant delay when scrolling... For this reason I decided to program my own list. This took me about two days, and not all functions are implemented yet, but I need a part of the code for the scrolling view for characters and backgrounds. So the time was not wasted. Furthermore I found out how to do DLL injections at runtime. I.e. LF2 must not even be able to load the DLL, but it all happens in the editor.

I also implemented another feature for the Easier Data-Editor yesterday. The feature will probably be deployed in the next days, but probably without a forum update post, because it is only a very small feature.

So the GIF mainly shows the runtime injection. But it also shows how I imagine a "Cheat Engine" for LF2.

Weeg 27 (original counter: 130) (14/07/2021)

After a very stressful time, I finally have some time again. And a small addition: In April, there was also less because I was busy with another LF2 project there. This project is also still in development, but will probably be quite useful for one or the other player ;)

First of all, I have updated the blog. This includes adding almost a year of development blogs, updating the url, updating the project name and updating the table. The development table looks a bit disappointing considering how long the project has been in development. However, it should be noted here that some editors are already finished in another programming language and just need to be adopted. But these will only be taken over when the Memory Viewer is ready. This is somewhat due to the version management and the idea of iterations.

This week I have also been working with the Memory Viewer again. The foundation has been implemented quite quickly (quicker than expected) and now it's mainly about making sure the software architecture is well thought out and displaying the values to the user. Displaying the values is not difficult per se, however I would also like to allow editing of Neora and other LF2 modifications. Therefore, the display should show everything automatically, without me as a developer having to do anything for the other versions. And it is precisely this code that must be legible and more so that editing is still possible in the future.

Weeg 26 (original counter: 128) (30/06/2021)

There is one piece of news that I have actually left out in the past, and that is the renaming of the project. I have published several editors for LF2. The initial name would only have confused people. For this reason I had chosen a new name. However, it wasn't until months later that I consulted a few people in the LF-Empire community to see what they thought. One person in particular said:

[...] calling it an editor is basically downplaying what its really supposed to do

For this reason, I came up with a new project name, after a lot of market research. In fact, finding a name is not so easy, because many suitable names are already in use. However, the new name is: LF2 Modding Environment (LF2ME).

User-friendly information about the project:
As I said before, I continue to work on the Memory Viewer, for displaying and editing data at runtime.

Weeg 25 (original counter: 127) (23/06/2021)

NOTE: Again, very much to the actual programming/development background. The editor is a very large project. Usually a large software is completed piece by piece. This "piece"/feature is developed into an iteration. When the iteration is reached, this feature is released. Now for me it makes no sense to release an "all round editor" in iterations. However, it is helpful as incentive, ideas, bug hunting, etc. if one would do this. For this reason, for the time being, I asked one person if they would be interested in participating in this. The answer was positive.

As mentioned before, I'm working with pipelines on this project. To be more efficient in the future, this week I've been working on having a task that automatically analyzes my code (using SonarQube), a task that automatically creates and uploads documentation, and a task that automatically creates and uploads the application to GitLab in different profiles ("Any CPU", x64-bit and x86-bit application). This means in the future I just need to create a git tag and a few minutes later everything is deployed automatically.

Furthermore, I started using tickets to manage the tasks.

User-friendly information about the project:
I started developing the "Memory Viewer", which is a kind of "Cheat Engine" specifically for LF2. The development of the Memory Viewer will continue in the coming weeks or months.