Jump to content

Lavenblade

Members
  • Content Count

    28
  • Joined

  • Last visited

  • Days Won

    1

Lavenblade last won the day on March 17 2017

Lavenblade had the most liked content!

About Lavenblade

  • Rank
    Member
  • Birthday 12/15/1992

Profile Information

  • Gender
    Male
  • Location:
    Washington
  • Emulator
    Hercules

Recent Profile Visitors

2105 profile views
  1. It's all finished on my end, just waiting for my pull request to be merged.
  2. I saw this thread recently so I opened up an issue and have started working on updating FluxCP to use Google reCaptcha V2. https://github.com/HerculesWS/FluxCP/issues/46
  3. Interesting. so something to do with permission then. Packing works here, maybe you need move patcher out ro client first or run packer in administrator. Ah, yeah it was a permission issue. I haven't disabled UAC on this new computer. 2.6.4.13b does not have any errors when executed outside OR inside the RO Client directory on a Windows 10 machine. Nice job. Hmm, with more recent testing Packing seems to fail a lot with 2.6.4.13b. Even when running as administrator. When it fails, there is a .tmp file that I can rename to .exe and it seems it actually packs it properly. The workaround is to just rename the temp file. Not sure why it fails though.
  4. Ah, I didn't realize they were all forks of one another. Thanks @@Dastgir
  5. I want to add on to this, actually. Why was C chosen over C++ respectively? @@evilpuncker How did they know better? Was there something wrong with using C++?
  6. I was under the assumption Hercules was following kRO behavior and not Aegis. If that is the case, I believe the report should have remained open and marked unconfirmed. Now to find someone who can confirm this...
  7. How do we go about testing kRO behavior?
  8. I saw that report you made. I feel like that report was tossed out too quickly. I was under the assumption that CT was unable to be reflected by any means. %Damage cards do not even effect CT. I've never seen CT be reflected by OL. Then again, I've never played official. I did see in your screenshots you were using RE. Are the behaviors maybe different in regards to Pre-RE vs RE? I am only familiar with Pre-RE. If this behavior can't be changed, I'd like an explaination of how it even makes sense... Almost certain Valk Mant and such also doesn't reflect CT... Maybe a toggle in the config is in order?
  9. Sweet, thanks for the suggestions.
  10. Surely with all of these developers around here, someone knows something?
  11. Hmm, can anyone confirm if the only way to do this is via hexing? If so, has anyone done this before? Can this be done with a simple find and replace? I have zero experience hexing, so I could not accomplish this alone. Perhaps something like this is straightforward and easy to accomplish. Looking for anymore insight if possible.
  12. I'm currently working on creating a new skin for my client. An example to get the idea of what I'm going for: However, the text on some windows are automatically generated. Meaning, it doesn't blend well with the colors I have selected. An example of the title below: Back to my question, is there any way at all to change the font color of all of the text that is output onto UI elements? All suggestions and solutions are appreciated!
  13. Interesting. so something to do with permission then. Packing works here, maybe you need move patcher out ro client first or run packer in administrator. Ah, yeah it was a permission issue. I haven't disabled UAC on this new computer. 2.6.4.13b does not have any errors when executed outside OR inside the RO Client directory on a Windows 10 machine. Nice job.
  14. I'm not sure if it makes a difference, but the error only occurs when the Thor Patcher is located in the directory of the RO Client. If it's located anywhere else in the file system, there is no error at all. EDIT: I tried to test 2.6.4.13b but I am not able to pack the configuration with ConfigGenerator.exe. It says that it fails. Packing works with 2.6.4.13 but not 2.6.4.13b.
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.