whats a UG moddeR?
You could, but you shouldn't. Think about it. You have a scroll that when you fail it's dura doesn't go down. But the dura of the item you are enchanting does. So you're gonna keep trying till you land it since scroll never breaks. But slowly you will break the item with each fail or god forbid huge fail *shudders*.Quote:
I found a function which is about -dura when fails, can I just make it returning 0's all the time?
Or you could just.... you know go to the call that it makes to the Standard.dll to determine success rates for pretty much every skill, its much easier to go to the source of all success rates than it is to go to change one skill. Everybody is so focused on the skill.dll since its the one that people seem to be "leaking", if you'd even call it that, modifications to.Quote:
Should be a Skill.dll edit
Thank you for your feedback :DQuote:
You could, but you shouldn't. Think about it. You have a scroll that when you fail it's dura doesn't go down. But the dura of the item you are enchanting does. So you're gonna keep trying till you land it since scroll never breaks. But slowly you will break the item with each fail or god forbid huge fail *shudders*.
Understanding assembly won't get you anywhere by itself. The files are huge. How will you find the function that... say... determines whether or not you need to aim? Sure, if I point it out to you, you might be able to easilly determine the necessary edit, but if I just say "here's a file, find the edit", you'll spend all day looking through subroutine after subroutine trying to RE each one.Quote:
Or you can understand assembly and what each function does, if you understand what each command does its very very very easy to understand what's going on. It's basically a simpler version of programming structure and logic, as long as you keep a hold of what every variable does and what is happening to the variable and why it's happening you can deconstruct everything yourself. Don't just look for constants and jumps, although those allow for the easiest modifications.
EDIT: Oh and as for the "underground", everybody rants about this "underground", who the hell cares about being part of an underground community, knowing assembly doesn't take a genius, if you took the day to completely dig around and play around with the dlls you could make so many useful modifications on your own.
core::CSkill<skillhere>Quote:
Understanding assembly won't get you anywhere by itself. The files are huge. How will you find the function that... say... determines whether or not you need to aim? Sure, if I point it out to you, you might be able to easilly determine the necessary edit, but if I just say "here's a file, find the edit", you'll spend all day looking through subroutine after subroutine trying to RE each one.
If you use IDA, look for core::<something goes here> and you find it.
Not using your tools is a prime example of stupidity. Take advantage of what you're given.
On that note, Who cares what this or that UG is doing. Doesn't concern you. I entirely agree with your point there =D
Not neccesarily. Dustins are not exactly a dime a dozen. Plus you still have to through pre-enchants some of which are not easy to get. So you still need to put in some hard work/money/dedication to make even one avenger dustin, let alone a thousand.Quote:
Does 100% enchant mod even exist?
If it did, im sure some smart person would've made more than a thousand avenger dustins by now..