summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authornullableVoidPtr <30564701+nullableVoidPtr@users.noreply.github.com>2019-01-26 02:50:10 +0800
committernullableVoidPtr <30564701+nullableVoidPtr@users.noreply.github.com>2019-01-26 02:50:10 +0800
commitf37626b175518b5f62ffcd50f05a96ffdb2d5e1d (patch)
tree003fc362ff6ad0e022b846f349728b1148e663a5
parente02183f66902e11b86c4e03e9ba4e8e3ad360e12 (diff)
Updated Why should I use this over binary hacking? (markdown)
-rw-r--r--Why-should-I-use-this-over-binary-hacking?.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/Why-should-I-use-this-over-binary-hacking?.md b/Why-should-I-use-this-over-binary-hacking?.md
index d2f303b..75ac552 100644
--- a/Why-should-I-use-this-over-binary-hacking?.md
+++ b/Why-should-I-use-this-over-binary-hacking?.md
@@ -9,4 +9,4 @@ Unlike binary hacking, one can easily change the size, locations, even the membe
*This is due to the incompleteness of the decompilations; for example, SaveBlock2 cannot be modified as of yet since there are many functions that reference it that are not decompiled.
-**Before you start hacking, it is recommended that you have some experience in coding in either: C, C#, Java, Go or Rust if you want to use use the decompilation.** \ No newline at end of file
+**Before you start hacking, it is recommended that you have some experience in coding in either: C, C#, Java, or any other C-like programming language, if you want to use use the decompilation.** \ No newline at end of file