- Joined
- Sep 27, 2016
- Messages
- 145
i tested it on my map .. im using command -save.. but its only saves 4 from 20 datas.. and it just ignore the remaining actions..
-
Listen to a special audio message from Bill Roper to the Hive Workshop community (Bill is a former Vice President of Blizzard Entertainment, Producer, Designer, Musician, Voice Actor) 🔗Click here to hear his message!
-
Read Evilhog's interview with Gregory Alper, the original composer of the music for WarCraft: Orcs & Humans 🔗Click here to read the full interview.
-
🏆 HD Modeling Contest #7 POLL is live! ✅ Vote for the TOP 3 MODELS! ❗️Poll closes April 28, 2025. 🎬Watch the entries on our YouTube channel! 🔗 Click here to cast your vote!
Maxou Save Load
- Author(s)
- blufflegendaire
- Size
- 23.36 KB
- Rating
- Downloads
- 90
- Created
- Apr 18, 2024
- Updated
- Apr 18, 2024
- Resources
- 1
- State
Approved
This bundle is marked as recommended. It works and satisfies the submission rules.
Just another save code system written from scratch.
Features in this save load
- Player name bound code
- Anti-tampering code
- Works with integers, avoids some floating number precision error corrupting some save codes (Pipedream save system -- used in Codeless -- suffers from this, at least, from my own experience, which is why I created this system in the first place)
Disclaimer
- This system is low level, it focuses only on saving into a code, and reading a code, if you want to write file to disk, you'll have to look around for the preload native.
- Saving your hero (or item) will require you to store their types into an array and save your hero (or item) index into that array (example included).
- Anything you want to save HAS to be turned into an integer, if you're trying to save floating numbers, define a precision and multiply as needed to achieve an integer representation.
- Warning : it can not save negative values.
This system is vJASS only, and not very suitable for GUI users.
Multiple examples provided inside the map.
Features in this save load
- Player name bound code
- Anti-tampering code
- Works with integers, avoids some floating number precision error corrupting some save codes (Pipedream save system -- used in Codeless -- suffers from this, at least, from my own experience, which is why I created this system in the first place)
Disclaimer
- This system is low level, it focuses only on saving into a code, and reading a code, if you want to write file to disk, you'll have to look around for the preload native.
- Saving your hero (or item) will require you to store their types into an array and save your hero (or item) index into that array (example included).
- Anything you want to save HAS to be turned into an integer, if you're trying to save floating numbers, define a precision and multiply as needed to achieve an integer representation.
- Warning : it can not save negative values.
This system is vJASS only, and not very suitable for GUI users.
Multiple examples provided inside the map.
Contents
Reviews
- Joined
- Jul 2, 2014
- Messages
- 51
Hello, could you share your code so I can have a look ?
- Joined
- Sep 27, 2016
- Messages
- 145
Now its fine, this sistem is good.. Thankyou..
- Joined
- Sep 27, 2016
- Messages
- 145
5/5 easy to learned..
Spell Reviewer
- Joined
- Dec 13, 2009
- Messages
- 982
A nice light-weight system for storing any type of data with a code. I like that it doesn't implement any specifics about what kind of data can be stored. This makes it very flexible and easy to use.
My main gripe is that you're using lower-case L and upper-case I as part of your charset. For a system that expects players to enter the code, that strikes me as just a very bad decision. These characters are nearly indifferentiable and I think should just not be used.
The SAVE_SIZE_STRICT_LESS_THAN variables, as far as I can tell, are unnecessary. I don't see why the user can't just enter any number specifying the maximum value of his stored integer and your script figures out how many bits you need at runtime.
Approved
My main gripe is that you're using lower-case L and upper-case I as part of your charset. For a system that expects players to enter the code, that strikes me as just a very bad decision. These characters are nearly indifferentiable and I think should just not be used.
The SAVE_SIZE_STRICT_LESS_THAN variables, as far as I can tell, are unnecessary. I don't see why the user can't just enter any number specifying the maximum value of his stored integer and your script figures out how many bits you need at runtime.
Approved
