I was messing around with xTera and was able to fix the issue caused by the May 24th update on my end. This is what I did:
1) Open xTera
2) Click "Tools," then click "Options." Now go to the "Advanced" tab.
3) By default, "Recommended Settings" is ticked. Instead, click on "Manually define Settings" and select that.
4) There should be a checked box called "Search Function" that has three settings in it. Those three settings are "Start Address," "End Address," and "Stack Size." "Start Address," as of now, is set to FB000000.
Change the B to A so it reads as FA000000 instead.
(Alternatively, changing the value to F9000000 will give some room in case of another Hex-changing patch.)
Thus, you should end up with something like this:
5) Click Save, and close xTera.
6) Re-open xTera and open Tera. You should be able to use xTera like normal now.
For those not familiar with Hexadecimal:
The values used to find the addresses in xTera are in Hexidecimal. From lowest value to highest value, these are the values used for one hex digit:
0123456789ABCDEF
...for a total of 16 "numbers" you can use.
On different country servers, the hex values may be slightly different. You may have to play with it a little to figure it out. I guess the new ninja class affected the hex values somehow? Anywho...
Not sure if this will fix it for everyone, but hopefully it does. :P