-
Notifications
You must be signed in to change notification settings - Fork 8
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
Refine DB Revamped & Refine UI support #10
base: master
Are you sure you want to change the base?
Conversation
Thanks to @cydh
Thanks to @anity99
Added a new configuration values in the YAML configuration to mark if a material will break or downgrade the item in case of failure.
… to @ecdarreola Signed-off-by: Cydh Ramdh <cydh@pservero.com>
# Conflicts: # src/map/script.cpp
* Updated it to the proper constant name.
# Conflicts: # conf/battle/feature.conf # db/re/refine_db.yml # npc/re/merchants/hd_refiner.txt # src/map/atcommand.cpp # src/map/battle.cpp # src/map/battle.hpp # src/map/clif.cpp # src/map/pc.hpp # src/map/script.cpp
# Conflicts: # conf/msg_conf/map_msg.conf
# Conflicts: # src/map/script.cpp
* Enabled Blacksmith Blessing check for refining to disable downrefine on fail! (of course without breaking the refined item) * +7 to +8 needs 1 ea * +8 to +9 needs 2 ea * +9 to +10 needs 4 ea * +10 to +11 needs 7 ea * +11 to +12 needs 11 ea * Added Blacksmith Blessing entries to refine_db.yml follow the values above. * Fixed refine_info clearances on loading files. Signed-off-by: Cydh Ramdh <cydh@pservero.com>
* HD Oridecon & HD Elunium only can be used to update equip with refine level +7 to +9. It means +7 -> +8, +8 -> +9, +9 -> +10. * Enriched Oridecon & Enriched Elunium are just replacement of normal materials. It means only can be used to refine up to +10. * Corrected `true = enriched` flag for `getequippercentrefinery` commands. HD just simply use normal rates, not enriched. Or create new value for HDs later Signed-off-by: Cydh Ramdh <cydh@pservero.com>
* You are now allowed to add your own refine costs/chances! * Say goodbye to `event_refine_chance` config. If you need 'event'-like chance, just add the chance value and use that type for `getequippercentrefinery` command, just like its bro `getequiprefinecost`. * To disable certain refine material (based on refine cost/type) on certain refine level/type, just remove its value from it! * The most important,see your refine_db.yml now, the refine rates are using refine cost types. If you have custom values, just simply adjust it. * There are Blessed Oridecon/Elunium from `blessed_refiner` NPC to refine_db.yml but it won't be displayed in NEW Refine UI, why? Because the `RefineUI` value in refine_db.yml is set as `false`. * technically Over +10 is 'normal' rates, just have different material, so the `REFINE_COST_NORMAL` never be in +11 to +20 so does `REFINE_COST_OVER10` will never be in below +10. There are also HD, Enriched, and Blessed ores with this refine level restriction. Signed-off-by: Cydh Ramdh <cydh@pservero.com>
* 'Break' is percentage number to break the equip on fail, 100 = 100% * 'DownRefine' is percentage number to downrefine the equip on fail, 100 = 100% (checked after 'Break' chance if passed) * 'DownRefineNum' is number of down refine
* `getblacksmithblessing(<type>,<refine>{,<var>})` to get info of Blacksmith Blessing usage for refining
* Removed unnecessary changes were changed on merge * Updated `getequippercentrefinery` to allow without type
Brog, voce ta usando o emulador dele ou voce pegou as mudanças que foram feitas nos arquivos e colocou direto no seu emulador? |
Could you update this for the latest version of rA? |
# Conflicts: # conf/battle/feature.conf # src/map/atcommand.cpp # src/map/battle.cpp # src/map/clif.cpp # src/map/clif_packetdb.hpp # src/map/script.cpp
Thank you! |
Sorry for the noob question but im using the latest rathena and is it possible to fetch this pull request? if yes then how? |
seems gonna make diff just for refine ui only without the script changes 🤔 |
@cydh crash on map_server:
|
Can you update this PR to the latest version of rAthena? Thank you |
@cydh please update. |
Working perfectly, thank you! |
is blessed ores not yet supported? its not showing on materials that i can use |
Hello @cydh , could you update to work with Lemon's PR? That of the new clients, using version 2020, the list of materials does not appear in the UI, only the blessing is showing, the other items appear as unknown. |
@cydh please update. |
Shadow items can be refined using RefineUI and use blacksmith's blessing even it is commented out on refine_db.yml |
@cydh Could you update this PR with the current rAthena? |
Excuse
A clean up of #9 that I updated it by merging it from master but one day I rebase it 🙊
The changes
Zero
The structures explained in this separated gist file. Read
One
Refine cost type is changed to
Two
Changed
getequippercentrefinery(<equipment slot>{,<enriched>,<char_id>})
To:
getequippercentrefinery(<equipment slot>,<type>{,<char_id>})
The enriched flag (boolean) is removed by type
Three
See on refine_db.yml, it's more
complicateddetailed now to support Refine UI that will show the correct materials based on equipment and its refine level, suchIf you are using custom refiner (that excluded from this changes) make sure you check again that I separated the
REFINE_COST_NORMAL
and normal forREFINE_COST_OVER10
, because before +10 for Armor as example needs Elunium but until +20 is Carnium. If you force to use 'REFINE_COST_NORMAL' for refining to +11, it gives you0%
success rate and gives no material ID.Four
About to 'separate' equip to its own materials (include chances and costs). Read this comment
Disclaimer
There are many credits by every commits, see yourself. Use this by your own risk such that maybe conflicted with your server or conflicted on future update on rAthena. I don't accept any support about "can you make it ..." related this changes, except as paid request.
This branch/PR includes