@Monkey_D_Luffy I've already done my research. There are no tutorials/guides/hints for my situation. Using my DOM parser, it is literally impossible to get the solution I need. It doesn't simulate any form of rendering. I can't think of any other solution. The time required for me to study the DOM parser and implement a rendering engine is very far from worth it. 

I don't know of any other solution and this might be the only other solution as far as I can think of and saw.

@Monkey_D_Luffy That doesn't fix the issue at all. <br> was just one example of many.

<p>hello</p><p>world</p><span>oof</span><a>blaaa</a>

Almost every visible HTML element pretty much starts a new render block. 

I'm already aware of the issue. The line counter is a plain-text line counter, not an HTML render block counter. I don't know how to count render blocks. That's why I added the scrollbar for overflowed text.

"<br><br><br><br>" Is one plain text line, but four HTML render blocks.

A developer marked Proxo as hidden for experimental reasons. I decided to remove it entirely because there was raised suspicion that they wanted to steal traffic from WRD for his own exploit website. This was all done by one of their developers who stole the project from the real creator. AnimeDeveloper explained this well above.

Thankfully, the real creator(AnimeDeveloper) has come back as the main developer. With the real creator coming back and removing Filter, we've been able to return back to normal. It just took a while for everything to be ready. Plans were made pretty much a couple days after Proxo was removed. I had stated in several places that Proxo was going to return eventually.

The creator has temporarily marked Coco Z as hidden. It wasn't removed. So they've told me at least.

@cujo915Thank you for confirming :)

@kylestewartThe non-memory leak version was released on the 29th. I reverted to the old module on the 30th because the new module didn't work for everyone. I will be returning the new version very soon. JJSploit is planned to have two injection buttons. One for the "classic" module and one for the new module. Not sure yet.

@cujo915 @CanadianWestern  I reverted the update causing this issue. You should no longer experience this.

@VirtualizationI've just now reverted the change due to various other issues arising like the intense lag for low-end PCs. Checking the module now will reflect the memory leak issue, but the GC on the "upgraded" module was pretty solid. I didn't notice issues with Owl Hub.

I saw that loadstring() was working. I saw that this script was working

loadstring("print'hi'")

I also saw that this was working

loadstring(game:HttpGet("https://cdn.wearedevs.net/scripts/Gravity Switch.txt"

Maybe something else in those scripts wasn't working with the new module. Doesn't matter now. I've just now reverted to the old module. I'll have to come up with a workaround in the morning if I want to involve the upgrades at all.

Check this thread to learn how to deal with the issue: https://wearedevs.net/forum/t/10995

I've fixed the issue. Thank you for the report!

What you just said is normal and expected behavior. The DLL I linked needs to be manually injected. I never said to replace the existing module.

@VirtualizationAre you sure you're referring to the updated module?

The module is always redownloaded by the WRD API. I didn't expect you to replace it. The DLL I linked needs to be manually injected. Thank you for the information! I'm starting to consider making a separate API version for the new update.