Jump to content

Alexiel

Members
  • Content count

    18
  • Joined

  • Last visited

Community Reputation

5 Neutral

About Alexiel

  1. Xigncode3 blocks Battleping :(

    BP 1.5.3 as well. Here's some more info in case it matters: Image: C:\Program Files (x86)\BattlePing\bp\ss5capcmd.exe Hashes: MD5=63A270F1917A4A2E35DF2D757E12D4A3 Image: C:\Program Files (x86)\BattlePing\bp\ss5capengine_battleping.exe Hashes: MD5=518C01615D840E76662B9723673F91F1 Image: C:\Program Files (x86)\BattlePing\wyUpdate.exe Hashes: MD5=0776370846DFE1D108CBD098DB162F35 Image: C:\Program Files (x86)\BattlePing\BattlePing.exe Hashes: MD5=3E8CC36CA11AA01EA0FAEF49E47048FC Image: C:\Programy\Lineage II\system\XignCode\xm.exe Hashes: MD5=8F0090C3A5499648EDE58D0CE2D5F620 ImageLoaded: C:\Windows\xhunter1.sys Hashes: MD5=6FB104855837F874765FC74BB071B676 Image: C:\Programy\Lineage II\system\AwesomiumProcess.exe Hashes: MD5=50D4FAA7C0091842C413F2F37E7F2A4A those files don't appear in sysmon log: x3.xem 555C976E6BD1C1D236A550E464DDABD9 xcorona_x64.xem 23E4E9D8840250C1ACE4451680082A58 xmag.xem 1F5F37EA63FA74D7BE86FE106B62D26B xnina.xem D823007EE752D81AE43DD6557873A96A xxd-0.xem & xxd-1.xem 37B5C33921042D203AB27166698671A1
  2. Xigncode3 blocks Battleping :(

    That's on win 7 x64. @BmD dude, please stop. When I forget to start BP I can instantly feel the delay. Like when I click on the ground, the char starts to move in about half a second. When I run on BP, the delay is what you'd expect, around 140-150ms (EU to TX and back). The difference is VERY noticeable. I made videos and measured this in FRAMES. Stop being a clown.
  3. Xigncode3 blocks Battleping :(

    I have never stopped using BP... https://imgur.com/g8717Dx
  4. AH Manager Bugged!

    It's not a bug. You just hit the display limit (999). Always refine your search and make sure the item list number is less than 999.
  5. Please nerf fishing ASAP!

    nothing is over, it has barely started
  6. Please nerf fishing ASAP!

    Exactly nothing will change about the queue when they turn off the raid event. People will just equip the fishing rods and start afking elsewhere.
  7. The servers are full for one reason - fishing. Anyone can clearly see it by checking the fishing areas. They are infested by keen fishermen. And when you start fishing yourself you quickly get the answer to the question why. Skillfull fisherman mission provides 500 free baits EVERY DAY. In 10 days of the free fishing rod from quest it means 5000 baits. Or even 5500 if you open the fishing rod pack and start fishing at the right time. All it requires is a level 20 toon (which is like 1 day of exp) and 5 baits (which you can buy instantly). Now let's say you don't want to invest anything into fishing, so you don't use shots. With those 5k baits and 20% fishing rate you get 592 blue and 390 fresh mackarel and 29 golden treasure chests (results may vary). You can either stop there and use all the free stuff, or you can turn the blue mackarel into more baits and go fishing again. 3 more rounds and you end up with no blue mackarel and 510 fresh blue mackarel and 38 golden treasure chests (again, results may vary). After 10 days of fishing rod you roll a new toon and rinse and repeat. Even the pro players playing only one toon are encouraged to log another two just for fishing, because it's automatic and provides various boosts for the main one (they can exp the sidekicks outside of CP time). The more computers you have, the more fishermen you must have. The worst thing is you don't even have to log another account too often, just relog the same account and keep creating new characters. And now imagine that bots can do all of this completely unattended. Fishing is not only self-sustainable, but OP, because everyone can play for free (no VIP requied), get level 20, get the 10-day fishing rod instantly and because the daily fishing mission is OP. This system may be fine in other territories where people have to pay for every account, but is too easily exploitable in free to play. I suggest to replace the daily mission reward (decrease the amount of baits to 24 or less, or put a completely different reward there, such as a non-tradable buff scroll, potion, etc.), or reduce the duration of the free fishing rod from quest (2 hours?), or both. This will dramatically decrease the amount of people online almost instantly. Thanks.
  8. Xincode Error

    Usually 2 (main + mentee, yes lol), sometimes 3. I've never had any problem.
  9. I fully support the idea to automatically abort macro looping after certain time. Just stop the running loop, so the player has to reactivate it again. (bonus points for making the delay random) One could still enable endless looping with the help of mouse/kb software, but GL making it work with 3 windows. Factions are easier now than ever. Defending macros through factions is silly. A game is supposed to be fun for people, not for computers. F*** bots.
  10. Xincode Error

    I always use BattlePing otherwise I get horrible delay in L2. I haven't noticed any problems with xigncode3 since monday, everything is fine for me. Windows 7 updated with latest patches, i5 4-core CPU, 32GB RAM, no AV running (long list of reasons why).
  11. Security vulnerability in XIGNCODE3

    Wait just a few more years and he will be state sponsored.
  12. Fishing Bait test :)

    So... I was in LoC tonight and today, Necro 105 + ISS duo, on macro without shots, around 20 hours in total (+-1h, can't remember exactly) and got 78M of pure adena and 97M in lvl2/3/4 mats (grocery price). 175M pure profit. It feels exceptionally rewarding. Fishing doesn't make sense, especially adena-wise. You must be extremely lazy to exp that way.
  13. Performance Issues Since Update

    In my case, the L2 game client uses around 1.2 CPU cores. The main game thread uses one whole core and the GPU driver thread uses ~20% of another core. I have an i5 3570k clocked at 4.3GHz. Mixa's CPU is 8C/16T (windows treats it as 16 cores) so his 6% roughly equals to 1 CPU core as well. I assume you have a 4-core CPU clocked around or below 3GHz... the 40% sound about right. A quick search led me to a 310-page unresolved topic on nvidia forums. If you're using win 10, roll back (or reinstall) your windows to build 1607 or even 1511 and block all feature updates. That should resolve the stuttering issue. AMD cards on win 10 don't stutter and nvidia on win 7 don't stutter either. You may consider that too.
  14. Security vulnerability in XIGNCODE3

    That "anybody" would have to escape the browser sandbox which is neither trivial nor cheap. Vulnerabilities get patched sooner or later. Wellbia is not a dead company so hope for a newer/patched version of xhunter until it gets to you.
×