Forum Replies Created
-
AuthorPosts
-
The above 2 are correct and this is the reason Miqo breaks every patch due to these codes changing, they are randomized as well which means every time they need to be sniffed out from the client files.
Obviously, Miqo is far more complex in terms of reading and interacting with things in-game, zones, UI etc… but in simple cases where it’s very minor hotfixes such as today’s patch notes, I would hazard a guess it’s a simple OP code update.
I’m no programmer/developer so they might say otherwise but I specialize in other IT areas enough to know the above will be correct to a degree. I’m sure they will sniff out the OP codes themselves instead of going off a simple member forum post but in their current situation if it helps then win.
It will be due to the OP Code changes each patch which SE decided to randomize for fun!
This patch the OP Codes are as follows:
StatusEffectList|90
StatusEffectList2|185
StatusEffectList3|de
BossStatusEffectList|36d
Ability1|130
Ability8|1df
Ability16|202
Ability24|bd
Ability32|14c
ActorCast|398
EffectResult|34b
EffectResultBasic|d9
ActorControl|2d3
ActorControlSelf|29b
ActorControlTarget|253
UpdateHpMpTp|2dc
PlayerSpawn|2c2
NpcSpawn|3cd
NpcSpawn2|7c
ActorMove|c2
ActorSetPos|22e
ActorGauge|11e
PresetWaymark|10f
Waymark|6f
SystemLogMessage|1f1EDIT:- Ignore attachment above, use this attachment, after running the scenario for an entire ET day I discovered another dodgy stop point that I’ve corrected for pewter ore in scenario 3
Attachments:
You must be logged in to view attached files.In step 1 of the scenario and change Waypoint 6 to Waypoint 18 for the destination and voula!
EDIT:- Attached is the exact change mentioned above.
- This reply was modified 2 years, 12 months ago by Betty Boo.
- This reply was modified 2 years, 12 months ago by Betty Boo.
Attachments:
You must be logged in to view attached files.Not sure what you are on about when it comes to GPU performance, I don’t see any GPU impact whatsoever and I’m on a Radeon 6800.
In terms of CPU performance, I see an impact of 3% to 4% from the application being open and idle.
I haven’t done any macro crafting yet since reopening but 15% doesn’t seem too unreasonable to be honest. -
AuthorPosts