Crafting fields & properties #1023
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
garrettluskey
requested changes
Nov 5, 2024
| { | ||
| Assert.True(client.ObjectManager.TryGetObject(craftingId, out Crafting clientCrafting)); | ||
| Assert.Equal(serverCrafting._currentHistoryIndex, clientCrafting._currentHistoryIndex); | ||
| Assert.Equal(serverCrafting._craftedItemObject, clientCrafting._craftedItemObject); |
There was a problem hiding this comment.
item object should have it's own handler and be treated as a network object
There was a problem hiding this comment.
Yeah, but that's a different issue. Or am I misunderstanding you?
There was a problem hiding this comment.
This is asserting the values are equal rather than a network string id
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
What is the new behavior?
Resolves #857
Resolves #856
Other information