The one I developed on hive is a lot more complex than Pipe's because it uses a tree based structure rather than an array. Mine is only useful if you want to save values that may or may not be present in the code, like item charges or hero specific gear ; ).
If all heroes can use all gear and you aren't saving any item charges, then Pipe's is just a lot easier to use and a better bet. There is another one I developed where you load the data in yourself etc (very low level) and it uses all of the latest security features, but if you don't know how save/load works and don't care too much about security, use Pipe's ; ).
You could use mine to save a little for heroes at max level (max level doesn't need to save xp), but the complexity of Encoder isn't worth that small amount you'd be saving.
Also be sure to save xp by percent-
http://www.hiveworkshop.com/forums/j...ercent-189943/
Keep in mind that if you have a level event and you use the above script, you could get some major crashes if you handle your level event sloppily =).
Anyways, here's a framework for mine if you want to check it out:
http://www.hiveworkshop.com/forums/s...6u%3DNestharus
On that thread, you can find examples for catalogs for hero specific gear and what not. I also did a catalog for hero specific abilities in the original demo map-
http://www.hiveworkshop.com/forums/s.../?prev=mmr%3D6
And if you understand the math behind save/load, you can use this one over Pipe's for improved security-
http://www.hiveworkshop.com/forums/s...mework-197557/
