View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0021805 | Return of Reckoning | General | public | 2023-12-15 21:27 | 2024-01-26 07:18 |
Reporter | Tesq | Assigned To | dalen | ||
Priority | normal | Severity | major | Reproducibility | always |
Status | closed | Resolution | fixed | ||
Summary | 0021805: General combat system problem | ||||
Description | There are several problem in tht combat system right now: 1- the script "/script Enemy.Print ('No target was marked yet')" dosent work anymore both macro and put into chat. This seems to be linked to a more general problem with combat system: 1- atm there are problem both firing melee skills in zergy sich ( error in computing distance / position between player moving) and especially use of ST punt. 3-also there is seems to be at least to me a huge chunk of healing done that get lost not counted in warband 4- the new combat system code also breaking enemy add-on, which is another indicator that something is off | ||||
Tags | No tags attached. | ||||
sy wrong copu/paste script this si the correct one: /script TextLogSetEnable("Combat", false) |
|
does "breaking enemy addon" mean that Enemy.Print macro isn't working? Or something else? | |
no it mean it randomly bug, such dont show who is guarded and who dont, or show ppl being guard when they arent, also doset show buff the script not working is the one post later because there was a copy/paste error /script TextLogSetEnable("Combat", false), this is the script for disabel combat log ( which i usefull to not have fps drop) litteraly a function of the client is not working atm and this is likely to impact other things. |
|
i found what is the problem with ST punt in game, they are considerated a cone of fire ability, thats the check the skill is doing and it prevent the punt especially when target is moving, i attach the screenshot with the error message | |
also the melee St skill range during pvp (and especialyl when ppl moving) seems too short, idk if its another problem linked to some kind of calulation done related to con of fire ability since i get no message. Just target ouf of range most of time | |
regarding melee distance for ST skills , it seems the "auto turn towards target" function inside client" is working similar to the cone of fire and causing similar problem liek the aobve for the punt. -normal pre patch "auto facing target"--> if the camera is not hold by use a skill the client will make the characetr turn towards the target, if camera is hold via mouse right click then the skill will fire but the character will remain faced in the camera direction (with no problem of skill firing or not) -post patch "auto facing target"-->in both case character will turn to face the target, it seems this causing a melee range problem when ppl moving while combat, it does not happen with static target because being static you can always face turn to him. The fix should be prevent "auto face turning" if player is holding camera. Step to reproduce: target any enemy entity, hold camera while facing the oposite direction, then press any usable skill. |
|
You are not supposed to be able to attack enemies behind you. Unless you stand still, then it will auto face the target. So seems to me this is working as intended. In default client settings you get a message on screen about this. Seems like you have those turned off. |
|
There is inside the client the "auto facing option" (its enable client side you cant test it in game in any static target it will turn your chars towards the enemy if you face opposite direction (i remember since i made the bug report on github ), before it was fixed in t1/t2 times your recived an error massage ( out of range); when you are facing opposite direction and press a skill your char will auto turn towards the enemey. In RVR before the patch this mean than in any direction you were facing you could hit target with sith st skills the important was only the actually range, the way it works now you are applying a hard check conve of fire on st punt ( wrong they arent ae effect so shouldn't be cone) and you are applying a pseudo cone of fire to all st skills in game which make attack camera wise hard for no actuall reason. The problem is in pvp ( rvr especially) while moving with camera, this cant work you need to be able able to look any direction for ST skills... atm you are forced to " manually look straigh" to your target and if its move in rvr with lag is impossible hit him with melee skill. IF you have a target in melee range and for whatever reason its not in that direction when you press the skill AND the skill wont work work......my BG cant even self buff with zerg moving all over + lag. This is too chuky to work in the long run. conve of fire and 360 degree area must only be applied to aoe skills AND not st ones. |
|
why is that even applied a cone of fire check or pseudo for st skills in first place....cuz you dont liek strife??? you alredy solved that fix vfx fix this make the combat just chunky you cant even assist properly with out a KD now. | |
Sounds to me like you are experiencing a lot of lag and that is your main issue. Maybe try using strafe keybinds as that allows you to adjust camera while moving and not get stuck in the out of range issues. | |
There hase been: 1-changes to vfx, 2-cone of fire, 3-melee st line of sight and i should have the internet issue? man it's not a latency problem. The only reason why there are fps drop in my screen is yet again due patch that changed /broken / not allow anymore the function /script TextLogSetEnable("Combat", false); Other wise i would not even have a noticeable fps drop under 300 vs 300 fights. Again there has been put too many check for pointless reason to melee skill, the strife alredy got fix via dmg/effet anchor to vfx |
|
I just tested /script TextLogSetEnabled("Combat", false) and it works just fine.... | |
i tested now and the chat keep send combat log text so nope, still not working | |
That is because you are using /script TextLogSetEnable("Combat", false) and when you are supposed to use /script TextLogSetEnabled("Combat", false). It is not Enable it is Enabled. Good luck you are on your own. | |
ankward but that is solved thx | |
Date Modified | Username | Field | Change |
---|---|---|---|
2023-12-15 21:27 | Tesq | New Issue | |
2023-12-15 21:28 | Tesq | Note Added: 0041717 | |
2023-12-16 10:55 | dalen | Note Added: 0041728 | |
2023-12-16 10:55 | dalen | Assigned To | => dalen |
2023-12-16 10:55 | dalen | Status | new => feedback |
2023-12-16 13:56 | Tesq | Note Added: 0041733 | |
2023-12-16 13:56 | Tesq | Status | feedback => assigned |
2023-12-18 12:13 | Tesq | Note Added: 0041773 | |
2023-12-18 12:13 | Tesq | File Added: Sintoras_000.jpg | |
2023-12-18 12:15 | Tesq | Note Added: 0041774 | |
2023-12-18 12:50 | Tesq | Note Added: 0041776 | |
2023-12-19 10:28 | dalen | Note Added: 0041833 | |
2023-12-19 10:30 | dalen | Note Edited: 0041833 | |
2023-12-19 16:09 | Tesq | Note Added: 0041841 | |
2023-12-19 16:14 | Tesq | Note Added: 0041842 | |
2023-12-19 17:25 | Tastykate | Note Added: 0041843 | |
2023-12-19 17:43 | Tesq | Note Added: 0041845 | |
2023-12-19 18:30 | Tastykate | Note Added: 0041846 | |
2023-12-19 23:57 | Tesq | Note Added: 0041849 | |
2023-12-20 00:39 | Tastykate | Note Added: 0041850 | |
2023-12-20 17:20 | Tesq | Note Added: 0041854 | |
2024-01-26 07:18 | dalen | Status | assigned => closed |
2024-01-26 07:18 | dalen | Resolution | open => fixed |