The problem is, if I use RSA encryption, for example, it would require large numbers which I don't think SC2 can handle. I'm not on my computer though, but I think that would be a problem.
Rollback Post to RevisionRollBack
Member since 2010. Made the -The Thing- [Revival] game. Nostalgic of the WC3 days.
"It's like patching the game without going through all the Blizzshit."
Viral: involving a piece of information that is circulated rapidly and widely from one Internet user to another. Bank: the only way to write non-volatile information into a computer from a SC2Map file. Injector: introduce or feed new information into a device.
If you haven't figured it out yet, this library aims to allow the mapper to inject information (strings to be exact) into every player's computer through viral means. It does require that one person starts this, but that will be you. It will also require that "infected" players continue playing to "infect" other players. For some games, this may not be the solution for you.
Why?
Publishing can be a pain in the ass: large uploads, failing uploads, slow uploads, logging in with the Editor. Sometimes it's just not worth it to increment the version of the game and ruining your patch notes. Much worse, the disappointed players who find out that the changes were a bit tiny.
So?
But you still need to tweak the game... Maybe for new announcements or for balancing; that's right, change movement speed, model path, sound path, damage, bans, or what not. Whatever coding can tweak, you can tweak with VBI.
How does it work?
Without going through all the functions first, simplest way to explain it: a bank will have a VBI string with a date, all the players will have their own bank with its own VBI string, you can compare them and determine what's latest with the date... which ever is the latest VBI string, it will be uploaded to the other players' banks.
Security?
The security is my own nooby encryption/locker system. Why my own? Because I can't download KrpytLib for some reason. Do I trust mine? Kind of. Maybe. I dunno, you tell me! But certainly, the VBI system will need all the protection it can get.
Character Code Locker
"It's shit, but it'll get the job done, right?"
It's an untested locking system that outputs an integer value as the checksum. This checksum is determined by several factors of a string: its characters, their position and their casing. Not particularly proud of this since I know there are more sophisticated encrypting systems in SC2. But then again, like I said, they're not available for download for some reason.
VBI & CCL PROGRESS
Fully featured. Documentation sucks, but I think I provided everything needed to know how to work this.
Feel free to moan for updates or you know, do it yourself. Share it though.
@ImperialGood: Go
I get you now.
The problem is, if I use RSA encryption, for example, it would require large numbers which I don't think SC2 can handle. I'm not on my computer though, but I think that would be a problem.
Member since 2010. Made the -The Thing- [Revival] game. Nostalgic of the WC3 days.
@willuwontu: Go
Ok.
Member since 2010. Made the -The Thing- [Revival] game. Nostalgic of the WC3 days.
@willuwontu: Go
Ok.
Member since 2010. Made the -The Thing- [Revival] game. Nostalgic of the WC3 days.
@willuwontu: Go
Ok.
Member since 2010. Made the -The Thing- [Revival] game. Nostalgic of the WC3 days.
Hey BurrittoTeeth, I hope this is acceptable now.
Viral Bank Injector
"It's like patching the game without going through all the Blizzshit."
Viral: involving a piece of information that is circulated rapidly and widely from one Internet user to another.
Bank: the only way to write non-volatile information into a computer from a SC2Map file.
Injector: introduce or feed new information into a device.
If you haven't figured it out yet, this library aims to allow the mapper to inject information (strings to be exact) into every player's computer through viral means. It does require that one person starts this, but that will be you. It will also require that "infected" players continue playing to "infect" other players. For some games, this may not be the solution for you.
Why?
Publishing can be a pain in the ass: large uploads, failing uploads, slow uploads, logging in with the Editor. Sometimes it's just not worth it to increment the version of the game and ruining your patch notes. Much worse, the disappointed players who find out that the changes were a bit tiny.
So?
But you still need to tweak the game... Maybe for new announcements or for balancing; that's right, change movement speed, model path, sound path, damage, bans, or what not. Whatever coding can tweak, you can tweak with VBI.
How does it work?
Without going through all the functions first, simplest way to explain it: a bank will have a VBI string with a date, all the players will have their own bank with its own VBI string, you can compare them and determine what's latest with the date... which ever is the latest VBI string, it will be uploaded to the other players' banks.
Security?
The security is my own nooby encryption/locker system. Why my own? Because I can't download KrpytLib for some reason. Do I trust mine? Kind of. Maybe. I dunno, you tell me! But certainly, the VBI system will need all the protection it can get.
Character Code Locker
"It's shit, but it'll get the job done, right?"
It's an untested locking system that outputs an integer value as the checksum. This checksum is determined by several factors of a string: its characters, their position and their casing. Not particularly proud of this since I know there are more sophisticated encrypting systems in SC2. But then again, like I said, they're not available for download for some reason.
VBI & CCL PROGRESS
Fully featured. Documentation sucks, but I think I provided everything needed to know how to work this.
Feel free to moan for updates or you know, do it yourself. Share it though.
DOWNLOAD & SCREENSHOTS
Asset Link
Member since 2010. Made the -The Thing- [Revival] game. Nostalgic of the WC3 days.