Just got on CA in about like a month, and I plugged in a TEXTURESCRIPTS.rez hack that I made a month ago that basically ups the ROF of the G36e, and it worked for a while but after i changed the ROF from "57" to "55", it just crashes when it gets to the login screen. even when i replaced the texturescripts.rez with a clean one it didn't work...
so im redowning right now. so anyone know if ROF editting is still ok? any limits?
Also i did just WinRezLT for extraction and 010 editor for the editting, so does that have any effect on the Rez checker?
Just got on CA in about like a month, and I plugged in a TEXTURESCRIPTS.rez hack that I made a month ago that basically ups the ROF of the G36e, and it worked for a while but after i changed the ROF from "57" to "55", it just crashes when it gets to the login screen. even when i replaced the texturescripts.rez with a clean one it didn't work...
so im redowning right now. so anyone know if ROF editting is still ok? any limits?
Also i did just WinRezLT for extraction and 010 editor for the editting, so does that have any effect on the Rez checker?
Check one of the newer guides in the tutorial section. Maybe your method is outdated. And if you did the texturescripts right it wouldn't DC.
Fix thread to speak English Pl0x
ok thanks, but when WinRezLT extracts a file from lets say Guns_M_PV_AR, does it actually take that ltb out? maybe thats why... O.o
Originally Posted by 3.14
ok thanks, but when WinRezLT extracts a file from lets say Guns_M_PV_AR, does it actually take that ltb out? maybe thats why... O.o
Maybe.
nevermind i got it... .REZ said that if you go below 55, nexon bitches at u. -_-
Originally Posted by 3.14
ok thanks, but when WinRezLT extracts a file from lets say Guns_M_PV_AR, does it actually take that ltb out? maybe thats why... O.o
Just use RezExtract, its easier to use IMO, and what it does is extracts the files to a folder that is created, so yes, you get the "actual" ltb, but its an exact copy of the origional