-
Notifications
You must be signed in to change notification settings - Fork 38
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
Arcade Account Improvements #543
Merged
Merged
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
* - implement new import AA screen - implement export private key button on arcade accounts * - finish check if arcade already stored * - fix overflow scrolling * clean
* - add minting lords screen - add check that it can't be an arcade * - remove need for connecting wallet - fix mint LORDS from AA (add permission) - implement fetch for supports interface * - fix blocking arcades on lords mint * fix build
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
- Adventurer Workaround: don't drop any items until you have full inventory 19/19 - Client Recommendation: don't let player drop any items until they have full inventory 19/19 - Every item dropped before 19/19 will result in an unusable inventory slot
havent tested - but looks logical |
@starknetdev - should we merge this? |
* Adventurer max level increases from 90 to 127 * Adventurer max strength and vitality increases from 15 to 31 --------- Co-authored-by: loothero <[email protected]>
* fixes failing tests in game entropy library * updates readme to be consistent with latest contract * updates repo to use starkli instead of legacy starknet * adds script to automate starkli account setup * adds script to automate contract deployment * adds DockerFile
* on v1.0.0 the idle counter is reset on every attack * adventurers can exploit this during certain battles to significantly prolong the duration of the battle which weakens the protection provided by the idle death penalty and global entropy sub-systems
This reverts commit c8f3c25.
This reverts commit 2a28283.
* allows clients to optimistically provide contract with the block hash for start_block + 1 * contract will verify provided hash was correct as part of highscore check and prior to minting collectible beast * contract provides a public slay_invalid_adventurers that can be used to slay adventurers started with wrong hash * this change is backwards compatible with existing clients. Calling attack() after 11 blocks will work same as it did previously but now clients can call set_starting_entropy(adventurer_id, block_hash) when start_block + 1 hash is available and proceed to call attack() immediately after.
* fixes quantum entanglement bug (metadata sharing) * includes test case for reproducing QE bug * includes test case for reproducing unusable inventory slots * includes additional test cases for stress testing inventory/metadata (temp commented out)
* hard codes contract genesis timestamp to V1.0 contract
* this can be removed after v1.1 optimistic start feature iis vetted on Sepolia
This reverts commit 78621f9.
* this can be reverted after v1.1 optimistic start feature is vetted on Sepolia.
- fix type issues
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.
No description provided.