RMMZ Only erase battlelogs after maximum lines have been reached

[Ejonkuo]

Hello! I've been searching for a while now everywhere (I even went to page 7 of google and did multiple searches on this forum ) for a plugin compatible with RPGMZ that allows me to modify the battlelogs, the x and y, the width, opacity, maximum number of lines and to clear the log only once the maximum amount of lines have been reached.
I managed to change those values with VisuMZ Battle core, but now I need for the battle logs to always stay and only erase the oldest log when the maximum line is exceeded. Of things that could help, I've encountered the following ones, among many plugins, and tried to use them through Fossil, however none work, even in a new project:

SRD Battle Log Upgrade
MPP Smooth Battle Log
Coolie_FF_Battle_Log
I don't want to ask for too much, but do remember that I'm using VisuMZ Battle core, so compatibility is preferred, but if it simply is not possible, I'd like for the plugin to allow me to adjust the aforementioned things too so I can use it as replacement.

Edit: Not gonna bump, but instead I'm gonna include an image of the progress, maybe it will help understand why this plugin is so important for the system I'm making.

 

[Ejonkuo]

Bump

 

[Ejonkuo]

Bump #2

 

[Ejonkuo]

Bump #3

 

[Ejonkuo]

Bump #4

 

[Ejonkuo]

Bump #5, Any help?

 

[Ejonkuo]

Bump.

 

[Mcniner]

Wow. I can see how this is frustrating. I'm sorry, I can't help you, but I have the same pain as you. I want this too.

 

[Ejonkuo]

Bump #7

 

[Arthran]

Are you trying to make it so that once the maximum lines is reached, it clears all lines and starts from the beginning again? Or do you want it to just erase the very oldest line, shift the other lines upward, and add the newest line at the bottom?

 

[Ejonkuo]

Are you trying to make it so that once the maximum lines is reached, it clears all lines and starts from the beginning again? Or do you want it to just erase the very oldest line, shift the other lines upward, and add the newest line at the bottom?

The latter, make it so that only the oldest line present is deleted, and the newest appears at the bottom indeed. That way the most important aspects of the fight can be kept for multiple turns until eventually replaced.

 

[Ejonkuo]

Bump #8

 

[Arthran]

If I'm correctly understanding your needs, then this should work. Make sure that it is lower than Battle Core in the plugin manager. I didn't test it too much, so let me know how it goes.

 

[Ejonkuo]

If I'm correctly understanding your needs, then this should work. Make sure that it is lower than Battle Core in the plugin manager. I didn't test it too much, so let me know how it goes.

Many, many thanks! Seems to be working fine and helps a lot with the aesthetic I was going for, though I do have to ask, Is there any way to erase all current displayed lines manually through an event?

I used "SceneManager._scene._logWindow.clear();" when I needed to manually clear all for one reason or another, however, that doesn't work anymore.

 

[Arthran]

Many, many thanks! Seems to be working fine and helps a lot with the aesthetic I was going for, though I do have to ask, Is there any way to erase all current displayed lines manually through an event?

I used "SceneManager._scene._logWindow.clear();" when I needed to manually clear all for one reason or another, however, that doesn't work anymore.

No problem. Unfortunately, that method of clearing the battle log won't work anymore, because I had to overwrite it, so I've added a new way to clear it. I edited my earlier post to upload a new version of the plugin. Please re-download it and use the new version instead. Please make sure to right click the plugin in your plugin manager and choose "Refresh", and make sure that it says that you're using version 1.01.

There is now a plugin command (named "Clear") that you can use the clear the battle log. Or if you prefer a script call, you can use:

SceneManager._scene._logWindow.clear(true);

 

[Ejonkuo]

No problem. Unfortunately, that method of clearing the battle log won't work anymore, because I had to overwrite it, so I've added a new way to clear it. I edited my earlier post to upload a new version of the plugin. Please re-download it and use the new version instead. Please make sure to right click the plugin in your plugin manager and choose "Refresh", and make sure that it says that you're using version 1.01.

There is now a plugin command (named "Clear") that you can use the clear the battle log. Or if you prefer a script call, you can use:

SceneManager._scene._logWindow.clear(true);

Many thanks again! It's pretty much everything that I needed!

However, there is a small issue that could be fixed, and that is that the actor and enemy damage logs, unlike all the other logs I believe, disappear unless the maximum lines has already been reached.
In other words, the log registering how much damage the enemy or actor received only stays after the maximum line of the log has been reached. I personally don't use damage numbers, but it's something to note.

Edit: Seems like missing/dodging the attack and receiving 0 damage also does that.

 

[Arthran]

Many thanks again! It's pretty much everything that I needed!

However, there is a small issue that could be fixed, and that is that the actor and enemy damage logs, unlike all the other logs I believe, disappear unless the maximum lines has already been reached.
In other words, the log registering how much damage the enemy or actor received only stays after the maximum line of the log has been reached. I personally don't use damage numbers, but it's something to note.

Edit: Seems like missing/dodging the attack and receiving 0 damage also does that.

You're welcome. Thanks for pointing that out. Since Battle Core hides those types of messages by default, I probably never would have noticed. I probably won't have time to mess with it for the next few days, but I'll fix it when I get the chance.

 

[Ejonkuo]

You're welcome. Thanks for pointing that out. Since Battle Core hides those types of messages by default, I probably never would have noticed. I probably won't have time to mess with it for the next few days, but I'll fix it when I get the chance.

I guess I could mark this as solved, but I'm not certain as I don't know if that prevents you from possibly updating the file?