Skip to content
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

Proximity items should be displayed in the Proximity items container #1149

Open
QuentinGruber opened this issue Nov 17, 2022 · 5 comments
Open
Labels
enhancement New feature or request gameplay no-issue-activity P3 priority 3 reverse Some reverse engineering is needed

Comments

@QuentinGruber
Copy link
Owner

image

  • Don't implement Proximity Container items since we don't have world containers rn.

#1147

@QuentinGruber QuentinGruber added enhancement New feature or request reverse Some reverse engineering is needed gameplay labels Nov 17, 2022
@QuentinGruber QuentinGruber added the P3 priority 3 label Feb 7, 2023
@Z1Meme
Copy link
Collaborator

Z1Meme commented Nov 2, 2023

Proximity items may be handled using an actual container that needs mounted to the character, needs reversed on client and gfx files.

Copy link

Stale issue message

@QuentinGruber
Copy link
Owner Author

Proximity items may be handled using an actual container that needs mounted to the character, needs reversed on client and gfx files.

@QuentinGruber QuentinGruber added this to the v0.32.0 milestone Jan 24, 2024
@QuentinGruber QuentinGruber modified the milestones: v0.32.0, v0.33.0 Feb 2, 2024
@QuentinGruber QuentinGruber modified the milestones: v0.33.0, v0.34.0 Feb 13, 2024
@QuentinGruber QuentinGruber removed this from the v0.34.0 milestone Mar 1, 2024
@QuentinGruber QuentinGruber added this to the v0.36.0 milestone Mar 13, 2024
Copy link

Stale issue message

@jasonmoonen
Copy link
Collaborator

Proximity items may be handled using an actual container that needs mounted to the character, needs reversed on client and gfx files.
if(Boolean(_loc4_ = new ProximityItemRow(this.m_dsProximityItems,_loc5_)) && !_loc4_.isWorldItem) { _loc3_.push(_loc4_); }

If we find where isWorldItem is set in the packets, it should work, I guess. I haven't found it yet

@QuentinGruber QuentinGruber modified the milestones: v0.36.0, V0.37.0 May 16, 2024
@QuentinGruber QuentinGruber removed this from the V0.37.0 milestone May 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request gameplay no-issue-activity P3 priority 3 reverse Some reverse engineering is needed
Projects
None yet
Development

No branches or pull requests

3 participants