Skip to content

Conversation

@vllsystems
Copy link
Contributor

Description

Implement the Wheel of Destiny system for OTClient.

Behavior

Actual

None

Expected

Players can open the Wheel of Destiny interface, view their skill specializations, and interact with the wheel nodes to allocate points.

Fixes

# (issue)

Type of change

Please delete options that are not relevant.

  • Wheel of Destiny graphical interface
  • Server data parsing (ResourceTypes.WHEEL_OF_DESTINY)
  • Specialized skills and points system
  • Integration with existing skills system
  • Informative tooltips for each wheel node
  • Visual animations and effects

How Has This Been Tested

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

  • Test A
  • Test B

Test Configuration:

  • Server Version: Canary Lastest
  • Client: OTCR Lastest
  • Operating System: Windows 10

Checklist

  • My code follows the style guidelines of this project
  • I have performed a self-review of my own code
  • I checked the PR checks reports
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works

@kokekanon
Copy link
Collaborator

kokekanon commented Sep 29, 2025

Do you need help? About six months ago, I did the cpp part(protocolparse). Do you want it?

@vllsystems
Copy link
Contributor Author

Do you need help? About six months ago, I did the cpp part(protocolparse). Do you want it?

ty @kokekanon
I'm not rushing; I'm doing it in my own time.

@vllsystems
Copy link
Contributor Author

A kind of roadmap would be good to guide the development. I'm still trying to understand some workings of the wheel before applying the nodes.

Refactor quadrant progress data to wod_information.lua
Add slot click handlers with border toggle functionality
Implement dynamic image updates based on progress frames
Load vocation-specific progress data with fallback to defaults
Fix slot widget hierarchy and event handling
@sonarqubecloud
Copy link

@vllsystems
Copy link
Contributor Author

vllsystems commented Oct 22, 2025

Do you need help? About six months ago, I did the cpp part(protocolparse). Do you want it?

20251022_162308.mp4

Greetings, Master Kokekanon.

Yes, we are going to need help. I believe it is a clip-image problem, as you can see in the video. The bottomLeft's node 5 is recognizing the 9, even though it is correct in Lua and the rest of the OTUI. Also, some nodes are "larger" than they should be.

Any idea how to solve this? I don't really know how clip-image works.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants