Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
I can't promise to make these consistently due to time constraints, but I do enjoy the process and wouldn't mind doing it every now and then if it helps out with the mod :)
0/3
While I was doing this I made several other changes, including a new way to handle reverse holos (meaning reverse holo cards no longer need to be duplicated within the set deck), a nicer way to handle most slots with more than 1 possible rarity, an auto-spread feature to easily see your pulls, and a switch to remove basic energy from packs (except when they are reverse holos).
1/3
Additionally, while I am only as far as Ruby Sapphire EX in my conversion from the old pack code to the new,I did research on packs and found 2 glaring errors in the old pack code.
Firstly legendary collection's commons and uncommons work far differently from what is intended. Specifically, the cards aren't shuffled at all! There's a fixed rotation of cards that covers the entire set and each pack starts in a random place in it, and then has the next 9 cards. The full order is here https://docs.google.com/document/d/1RPpLfoJ109k0X88iKRQ0ZpjIup35lfqi3XsZCXx3RY8/edit?usp=sharing .
2/3
I have already made these fixes in my new pack code, but am not sure what to do from here. Should I upload my own version of the mod? Discuss changes here? Organise things in a discord?
3/3
Thanks for the fix, I assumed it would be more complicated so didn't initially bother, but it was a quick solution and should be easy to implement going forward as well. Thanks for the tip!