I can reassure you that that's a false positive. I was just cracking open this .bat file about 2~3 days ago to see if I can (sanely) modify it for the prime mod. I can literally tell you what every step of this .bat file does. Truth be told, a lot of antivirus these days just assume any and all scripts for windows from the internet are malicious. But if I had to hazard a guess as to which part(s) offended it, it would be these type of lines:
Code:
powershell.exe -nologo -noprofile -noninteractive -command "& { [IO.File]::WriteAllBytes(\"%rpatoolps%\", [Convert]::FromBase64String([IO.File]::ReadAllText(\"%rpatoolps%.tmp\"))) }"If you want, I can tell you how to reproduce the steps, manually, of what this .bat does so you don't have worry about the .bat being malicious. It's not really hard, just tedious.
Other than that, you're just gonna have to trust that it's a false positive or, if you have cygwin installed, you can try my linux version as that is much similar due to how much simpler it is due to what toolset linux command line provides.
- Apr 27, 2017
- 1,034
- 1,181
No need, just testing the water a bit to see if it's kosher before i use it, this site is surprisingly clean even by pirate standards.
That's what happens when you have accountability and moderation. (^^)b
- Apr 10, 2019
- 78
- 53
Yes and no. I have a linux version and that's working just fine. The windows version would take a good amount of effort to do, at least, automatically. Basically, because the prime mod doesn't include the .rpy files (just the .rpyc), I'd need to include unren into the .bat file and that's a REALLY big hassle (there's 2 ways to run unren. One requires that you start the game once. The other requires the entire source code for unren to be present.). The alternative is if someone manually runs rpatool and unren manually and the .bat file can do the rest.
If you want, I can do a semi-hack way to apply it, and it'll work. It just won't be as pretty or as easy as the original cheat injector.
- Apr 10, 2019
- 78
- 53
I'd really appreciate you doing the semi-hack. I used to know how to unren but that was years ago and I've forgotten how to do it now. Why does the windows version take more effort to make work than then linux version?
Lots of reasons. Neither powershell nor command prompt works as well nor has as many tools available nor as easy to link together as bash. A good example is that the original .bat, SLDR has to store rpatool as a a base64 string which, in the windows side, has a size limit. In my linux version, it just runs wget to download the latest rpatool from the repository. And that's ignoring needing to use a scripting language to more easily to file manipulation where as, I can run sed or awk or perl to do the same thing.
I should have some time tomorrow. I'll see if I can get done then.
- Apr 10, 2019
- 78
- 53
I. HATE. Windows. (Particularly programming/scripting for it.)
With that said, it's done. I put a little more polish into it. Download it, rename it to .bat, run it, and make sure to
--->READ THE INSTRUCTIONS.<-----
I'm not emphasizing that to suggest or insinuate anything, but rather, since this cheat takes longer and more steps than the original cheat injector, it can be easy to miss if you're not paying attention.
Tell me if you run into errors. I've been able to run it 2~3 times without a problem on my windows partition so it should be fine but things happen.
Also, unlike most of my code, I'm not making a repository or anything for this. This will be the ONLY copy of this cheat injector. Pretty much made specifically for you. So, if it gets lost from this forum and/or your drive, it's pretty much gone. So, if it's useful for you, make a backup of it.
Last edited:
- Apr 10, 2019
- 78
- 53
Thanks for doing this. I'm not fully sure how I'm supposed to get this to work though. I'm assuming I just delete everything before the DO NOT EDIT BELOW THIS LINE part then change the txt file to a bat file and run it in the folder with the exe in it. I downloaded rpatool from the link in the text file and unren from here:
You must be registered to see the links
. Not sure what to do with them though.
Oh, you don't do any of that.
Here's what you do, start to finish:
- Download the .txt file I posted into the "game" folder for Rogue-Like w/ Prime mod.
- Rename it from .txt to .bat
- Double click the .bat file to run it. It'll open up a command prompt.
- Follow the instructions on the prompt.
- Apr 10, 2019
- 78
- 53
It works! That was a lot easier than I thought. Thanks a lot
No problem. Thank you for confirming that it works.
I try to make all my stuff pretty user friendly without encroaching on logistics or functionality. But sometimes that's a hard line to walk considering the varied technology aptitude different people have as well as the OS that they have. The hoops I had to jump through to make it user friendly for windows was pretty obscene.
Glad it works. Have fun. ^^b
Are you running my RLE prime cheat injector against non-Prime-mod RLE?
If yes, please use the original cheat injector.
If no, please refer to this post.
Also, please note that you don't have to "run the game quickly". In fact, you have to do the opposite and let it do it's thing and follow instructions *when it tells you to and not any time sooner*. Both extracting and decompiling can take a bit so when you've started the .bat file, let it run until it tells you to close it and start the game. When you start the game, wait until it gets to the title screen. Don't just double click the .exe then kill/quit the process immediately. Basically, make sure to follow the instructions and don't rush. The prime mod hasn't changed, it's confirmed to work on 2 different machines half a world apart.
- Jun 15, 2021
- 871
- 1,294
I think this might be a Windows 11 problem, but it's throwing me an error; "'powershell.exe' is not recognized as an internal or external command, operable program or batch file." Not sure where to go off of this.
Powershell is a windows program. Remember command prompt? Or the dos prompt? Powershell is/was suppose to be the advance version of that. It *should* be installed by default. If it's not, try installing it manually.
It's also possible this has something to do with it:
You must be registered to see the links
I can't imagine MS being dumb enough to hide powershell behind the terminal app but they've done worse before. Either way, give it a shot.
I actually wouldn't do that as/call that a fix. If powershell is missing from the system variable "Path" it could mean other things. Like a bad update, system being corrupted, system was compromised, it's not turned on as a feature, just plain not installed because the OEM version of windows someone is using has it turned off, group policy, etc.
If the path to powershell is missing, it needs to be added as part of "Path". Instructions on how to do that
You must be registered to see the links
(note how, even in this article, the path to powershell is already part of the the system variable "Path"). Because adding that path to the script would just fix it for this script, but also ignore the fact that MS is trying to move to powershell v2. If/when v1 is deprecated, the absolute path in the script would break the script.The better solution is to make sure it's installed. If it isn't (or if it's reinstalled) it should write the path to it into "Path".