-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Openkore not detecting correct Ammo count/Not detecting Ammo when equipped #3943
Comments
We need more logs |
provide servers.txt and more logs |
Thank you. I will gather the logs and send them here. |
Hopefully got the needed files |
@Ome3370 about issue: and remove the following code:
|
Hi @alisonrag I apologize but I'm not sure where or how to do the encryption. |
Hi @alisonrag so I was able to locate the file and delete the code mentioned above. Note: Not sure if this would be helpful but I found out that this only happens when the arrow is equipped. It does count it accurately when not equipped. I did a work around to unequip the arrows manually and then open the program and will equip there. It does work but kinda hassle to do everytime you need to re-open the program. |
@Ome3370 How do you connect to the server? This server uses bot protection |
------------------ Openkore Issues Template ------------------
-- OpenKore what-will-become-2.1 ( version ctime:2024_10_10 ) - Custom Ragnarok Online client
RO ASIA
BUG
Hi Guys,
I'm fairly new here so I apologize if it may look that I wanted to be spoonfed.
I'm having trouble with the openkore client not detecting the correct number of ammunition (GS/Rebel Bullet ) or not detecting them at all if equipped. Sometimes it detects the ammo when equipped but unable to count the right quantity. I noticed this happened after our recent server maintenance. This affects the capability of using the ammo as trigger to automatically get from Kafra.
I have tried searching but unable to find the exact issue. Thank you in advance.
Let me know if you need more information.
The text was updated successfully, but these errors were encountered: