Jump to content

Recommended Posts

Posted

Well I use dyes like this:

 

PVE:

Dye: +4str/-4 Dex (-4 dex doesn't take off a lot of critical rate/evasion, better than take off -4 CON in DE figther)

 

PVP: +4 STR/-4 CON

 

Skills: Just use dead eye when you're buffed with haste lvl2/zerk or any other buff for atck. speed

Dont use hex evertime when you're grinding/pvping, its kinda a waste of mana if you play in low rate servers.

 

PR is a nice archer for pvp, Imo its the best, coz it has hex/power break,dead eye, evade shot etc.. with time you'll learn how to play nicely.

Posted

Dyez: +4STR -4CON and Sometimes +2DEX - 2CON

I know Low HP is dangerous but if you are good enough you can pwn all.

 

Skills:

Buff you self with Dead Eye, and all the Arrows Buffs.

 

Pvping/Pking

Only use hex if the Target is looking at you. If you are seeing hes back Stun him and then hit him/her with Pink Arrow Skill (Lvl 76+).

And continue DoubleSHooting or Stuning at Him/her.

Posted

if make pvp vs any tank.... first ; Freezing Strike  and  run and Hex and  run and Stunning Shot  if is failed run and Power Break and stop and hit hit hit and winer :)

Posted

never go -CON in PR

D.ELFS are already stun magnets,if u go - CON u will loose from 20 lvl tank

 

in pvps use hex and if u play on low rate spam skills

try to avoid 1 one 1,your true power is to hide (extreme low pdef / hp / 1 / 1/1 stunned)

and hit (extreme high patk/critical dmg)

PR is the best class for mass/siege pvp,when u have healer/support

u can 2 shot almost all robe users

Posted

never go -CON in PR

D.ELFS are already stun magnets,if u go - CON u will loose from 20 lvl tank

 

in pvps use hex and if u play on low rate spam skills

try to avoid 1 one 1,your true power is to hide (extreme low pdef / hp / 1 / 1/1 stunned)

and hit (extreme high patk/critical dmg)

PR is the best class for mass/siege pvp,when u have healer/support

u can 2 shot almost all robe users

 

i agree DE never there good with HP so why to take it off more ?! maybe for dyes just put -dex + str better i think

Posted

if make pvp vs any tank.... first ; Freezing Strike  and  run and Hex and  run and Stunning Shot  if is failed run and Power Break and stop and hit hit hit and winer :)

tank>archer ,tank too have freezing strike-entagle-shackle or roots when tank have cp pots,you only can use soe;]

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now


  • Posts

    • And Discord: https://discord.gg/3aYqWNqb
    • Ofc: https://discord.gg/3aYqWNqb
    • You can find some H5 skins shared in old L2 modding Discords, but most of the higher‑quality ones are either paid or come bundled with full client edits. I usually mix in commissioned work and whatever I can patch myself. On a side note, I fund a lot of these commissions by selling off game items through instant sell cs2 skins, which has been a quick way for me to get some cash for projects.
    • There is no need for gRPC in this case, even tho originally it was gRPC based but since we don't need it to be bi-directional, we switched to simple http requests for the web calls and SSEs for the data streamed from the server. There are distributed locks in place to precent race conditions between actions that can happen between multiple web instances and the server.   Local models can also be slow depending on the model, and most external models can actually be faster than local ones if you use Flash 2.5 or something along those lines. I am running on 512GB of Unified Memory on my Mac Studio M3 Ultra so the speed of the local model for a small model is pretty good but I tested it with Gemini too and it works equally as fast and in some cases faster. The way it works is that I'm using pgvector (one of the benefits of moving to Postgres) to search the data and see what the player can see etc and there is some batching of the next few actions for 2-4 seconds for the user until the next LLM request fires. The batching also includes branching on logic so if they for example fall under some HP they will move to kiting instead of attacking or maybe they heal etc.   Everything is authed and permission-based. The server and the backend of the frontend have secure communication between them, either with a symmetric key (not recommended for production) or a certificate (the recommended way), so there is no worry. It's all tied to the account's access level, etc., so nobody can make an action that they normally wouldn't be allowed to do. Even the MCP is token-based, and there are prompt injection protections in place. The MCP is audited, and every mutation needs confirmation. The admin area is only accessible to the admin account anyway so normal users can't access it.  
  • Topics

×
×
  • Create New...

Important Information

This community uses essential cookies to function properly. Non-essential cookies and third-party services are used only with your consent. Read our Privacy Policy and We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue..