Skip to content
GitLab
    • Explore Projects Groups Snippets
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • 2 2006Scape
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 25
    • Issues 25
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 9
    • Merge requests 9
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • 2006Scape
  • 2006Scape
  • Issues
  • #59
An error occurred while fetching the assigned iteration of the selected issue.
Closed
Open
Issue created 5 years ago by Dark98@Dark98Owner
  • New related issue

  • New related issue

Trading system flaws

Closed

Trading system flaws

Created by: Gptaqbc

It seems there is a problem with the coding of the trading system between players. I tested it this week-end and here are my observations.

I'll explain the expected process:

P1 clicks trade on P2; P1 moves next to P2 to send him the request; P2 receive and accpet the request; Trade screen opens; -- Anything happening here that isn't adding/removing items or accepting in the trade screen abort the trade process --- P1 & P2 accepts screen 1; -- Anything happening here that accepting in the trade screen abort the trade process --- P1 & P2 accepts screen 2;

Trade completed

Here's a list of the problem with our trading system:

  • After the trade request is sent (click trade player) both players doesn't have to be next to each other to initiate the trading process and complete the trade.
  • A player can quit the trade screen by clicking the minimap but it's not declining it for the other player. Let's call this solo trading interface.
  • When a player is stuck in the solo trading interface he can still fill the trade screen with items. If the other player that initiated the trade proceed to logout, the trade screen will close but the items will stay in the trade screen until the players trade again. This is a big issues as it can expand the inventory by 28 slots for every player.
  1. Oh no!

    You are trying to upload something other than an image. Please upload a .png, .jpg, .jpeg, .gif, .bmp, .tiff or .ico.

    Incoming!

    Drop your designs to start your upload.
Tasks
0
server returned results with length 1, expected length of 3

Linked items
0

Link issues together to show that they're related or that one is blocking others. Learn more.

Related merge requests

Activity


  • Dark98
    Dark98 @Dark98 · 5 years ago
    Author Owner

    Created by: Gptaqbc

    Here: https://github.com/dginovker/2006rebotted/blob/ea513131259e183017476cb3177649c804a35af9/2006Redone%20Server/src/redone/net/packets/impl/ClickingStuff.java#L34

    player.getTrading().declineTrade();

    What about adding oponnent.getTrading().declineTrade(); too? That should close the trade screen for both players. That should fix the issue with being able to store items in the trading interface. I'll try soon.

  • Dark98 added Difficulty: Medium label 5 years ago

    added Difficulty: Medium label

  • Dark98
    Dark98 @Dark98 · 5 years ago
    Author Owner

    Created by: Gptaqbc

    Almost completed. Can you assign me on the issue?

  • Dark98 mentioned in merge request !117 (merged) 5 years ago

    mentioned in merge request !117 (merged)

  • Dark98 closed 5 years ago

    closed

Please register or sign in to reply
0 Assignees
None
Assign to
Epic
No epic
None
Labels
0
None
0
None
    Assign labels
  • Manage project labels

Milestone
No milestone
None
Iteration
No iteration
None
Weight
None
None
Due date
None
None
None
Time tracking
No estimate or time spent
Health status

None

None

    Assign health status


Confidentiality
Not confidential
Not confidential

You are going to turn on confidentiality. Only project members with at least the Reporter role, the author, and assignees can view or be notified about this issue.

Lock issue
Unlocked
0
0 participants
Reference:

Menu

Explore Projects Groups Snippets