3/20/10 LF2 DLL Framework Update

[1477]

Hello Guys!

Included and attached to this post are the updated versions of the DLL by Silva, along with the demanded 'Charge Attack' feature requested so far.

There are three versions of the DLL. These are the DLLs intended for the original, no num-lock, and 2.0a versions. Users, please test these DLLs all-out, and let me know if there are any problems. I have not myself fully tested them.

Additionally, I have decided to upload the engines, or the EXEs for all of the three versions, prepared and ready to run the DLLs on click .

If you would like to modify a different Engine other than the one included at the bottom of this post, please refer to the instructions by Silva, which can be found here: >Patching EXE/Engine to Load DLL<.

Mods, please let this thread remain independent if it does not trouble you too much, because the official DLL thread is long dead.

The password for them all is LFE.


Personal Note to Current Hex-Coding "Pursuers":

Please try to not to burden this thread with DLL questions. Start up your own thread for this matter. The content in the DLL most likely works. If it doesn't, please ask someone else that possesses hex knowledge, and they will help you. I do not hold responsibility for Silva's nor Genevrier's old coding, and through my means of coding analysis I have yet to detect any errors (HP and MP are Genevrier, I think). If you insist on asking questions, again create a new thread in the 2.0 Editing section, and direct it at somebody else. I am now only present on LFE once a month, and only then to post any curious updates that I have stumbled upon during my own exploits of the LF2 engine, since I have a personal, LFCL-dedicated DLL that contains many other useless-ish features I stuff in for simply 'teh lulz' and don't include in the LFE version...

Basically, what I'm saying is, I am and will continue to ignore hex questions simply because I do not have the time to camp on this forum and answer them. If you haven't already noticed, then this is a confirmation. Please enjoy the features I posted, and not greedily add them to your mod simply because they exist and you've got to utilize them in order to make it appear unique and good . <- This often leads to a chain of never-ending "wants", since DC has a set, defined limit of impossibility, whereas Hex really does not. Please don't take any offense to this message, I am simply trying to explain my personal ignorance to the questions out there regarding the DLL ever since Silva rage quit. Thank you for reading, guys!

---

DLL Update History (Click to View)

'Holding' Feature Explanation:

This is the explanation for the new 'Holding' Feature that I have implemented into the DLL.

States:

State 21 - Holding Left
State 22 - Holding Right
State 23 - Holding Attack
State 24 - Holding Jump
State 25 - Holding Defend

If the button is held down, then nothing happens. The frame will continue as if normal. If the button is not held down, then the frame will be automatically incremented by one.

Updated States:

State 21 - Holding Forward
State 22 - Holding Backward

Since there is a maximum limit of 5 attachments per post...
Look Here for the Download Links to the Updated Versions:

12.2.10 DLL Framework Update<

March 20, 2010 Update:

Fixed Holding Forward/Backward States (21 and 22)
Fixed 99.9% Time-Stop
Created Object-Oriented Itr/Kind 8 BETA

Time-Stop Explanation:

Nothing much, fixed some memory allocation issues, and funky memory access stuff that Silva errored in his version (that was still untouched from the last update).

Object-Oriented Itr/Kind 8 Explanation:

Well, it's been a long time since us DCers have had a horrible time getting objects to "stick" properly. The identical ID dilemma has been an unsolved problem since all the way back to the beginning of modding. As a result, in order to insure perfect execution, some DCers have limited the associated features to these "sticky objects" to stage mode, where they can restrict the number of simultaneous players down to only one. Yet the problem of identical AI characters still arises...

In order to attempt at combating this problem, I've managed to create a prototype version of an object number-oriented itr/kind 8 effect. By identifying characters by the Game Engine's object tags instead of the common ID numbers, I managed to create a "definitely-unique" itr/kind 8 effect. This means character Special Bars, Simon's Stamina Bar, Zxcv's Wall-Running "sticky", Ball Shields, etc. can execute perfectly without interference.

However, my code is currently only a prototype at most, which means there will definitely exist some bugs. A known one is that, even though the object only "sticks" to one character, the sticking object can still technically be "stopped" when the character passes another. The other character will not "pick up" the object, but the object will still "stop" in its movement. Hard to explain, you'll see when you try it out. In order to minimize this issue, still utilize "special coordinates" for your characters.

Now for the Itr numbers...

Itr/Kind 824: Object-Oriented Itr/Kind 8 for Type 0 Prototype
Itr/Kind 825: Object-Oriented Itr/Kind 8 for Type 3 Prototype

P.S. - Some stuff to look forward to...

Time-Stop In A Ball
TBD Exploits of State: 20

Download Links: Yay! They're permanent now.

>1.1.10 LF2 DLL Engines<
>20.3.10 LF2 v2.0 DLL<
>20.3.10 LF2 v2.0 No-Num DLL<
>20.3.10 LF2 v2.0a DLL<

Update 3/22/10: Perm Links loaded ftw!
New thing to look forward to next update!
- Hex "HP-Requirement" Fix!

Happy DCing! See you all next month!


~Solomon Leung

[krystian2160]

Can you upload the exe + dll ?

[Bedi122]

Very good job man! I am happy

[sanji207]

If i change any pictures in 2.0a exe with resource hacker,exe isn't work...

[1477]

In order to change pictures with ResHack, you need to change the pictures before patching the engine.

Since the engine that I posted is already patched beforehand, one cannot change the pictures.

In order to change the pictures, you need to learn how to patch it yourself. Again, detailed instructions on how to accomplish this can be found here: >Patching EXE/Engine to Load DLL<.

Remember, you need to change the pictures first before patching the engine.

@hkmnhkmn

I have no idea why it doesn't work for you, maybe the password? It is 'lfe', with all lower case/no caps.
The RAR isn't broken for sure...

Here are additional links, with the password in MediaFire instead of the RAR itself...

>DLL Engines<
>LF2 Version 2.0 Original<
>LF2 Version 2.0 No-Num<
>LF2 Version 2.0a<

*Links Disabled* to avoid confusion.

Again, the password is 'lfe', all lower-case.

Enjoy your New Year, guys!


~Solomon Leung

[hkmnhkmn]

It says something like "please make sure there are enough space for you drive and the file is not being protected .Check if the file is using right now"

[krystian2160]

Bedi LOL!
Do you speak Engilsh ?

[Sharingan]

Found a bug in states 21 & 22 (left & right)!
When u're facing right and holding right (state 22) then is ok, but if u're facing left u must holding also right (state 22) (0o)
and it's strange when i'm charging something holding right on both sides.

Btw maybe u should do states other way.
4 example state 24xxx (if u're holding jump then u're going to frame xxx otherwise u're going to next frame).

And maybe add holding up and down button.

[TheNave]

@1477
you should change Right and Left in Forwards and Backwards instead... that would be better

[sanji207]

I put pictures into 2.0A EXE, but when adding DLL
Parameter is the call dword ptr [d20140].............
if i add it,OllyDBG is"unknown identifier"