Questions about Memory Editing - Cypher

[Gamer]

When learning a new language, unless there's a good reason for me to do so, I don't wanna learn a brand new syntax, thats just a ****ing waste of time.

/Agreed. The reason I'm personally using VB at the moment is that I was forced into learning it as part of high school software dev classes, and I haven't yet (although I'm sure to in the future) encountered an instance where VB isn't giving me the functionality I need.

I know the transition to a C-style language is inevitable though. From a fairly good grasp of VB would you recommend moving to C# to get the C-style syntax with the .NET familiarity or just moving straight to C++?

[argh44z]

Mentioning something just because 'noone else did' is retarded, theres probably a good reason noone mentioned it.

I guess you're right in some cases. In this particular case, python doesn't really have mindshare on win32 compared to other high level languages (as opposed to other platforms). That doesn't mean it isn't a good choice however. I'm just throwing the name out there because many-a ye random VB/autoit developers have likely never heard of it. Almost all more experienced programmers have.

Anyway, you're spot on that for the purposes of memory reading/writing/hacking, using the language that the game was developed in (or in some cases whatever the underlying operating system has it's native APIs in) is nearly always going to be the best choice.

[arigity]

I'm sorry, but imo "default to the easiest" is a terrible suggestion. If you don't know a programming language why double-handle? Start with one that can help you understand the topic better (C++).

i say default to the easiest, because people who learn a language specifically for the purpose of memory editing are likely to learn only a specific portion of the language and would have a much easier time with something thats simple and easy to understand even for a beginner.
this might not be the best solution programming-wise but as far as working code goes you would be better off with something easy to understand.

VB is terrible, both in terms of the language itself, and in terms of the functionality it lacks in terms of a similar but much better language (C#) -- do a google search if you think VB == C# and only the syntax is different, you'll find you're quite wrong if that is the case. There is absolutely no reason to use VB unless you fail to meet the IQ bar required to learn C# (which is not high at all), don't ask me why people have trouble learning C# when its so similar to VB, but it seems that C-style syntax confuses the **** out of some people.

ok, VB supports bad programming habbits, and yes C# does have some functionality that VB doesn't, but that extra bit of functionality isn't exactly large, the differences are minor at best. and unless your counting syntax i have no idea how you can say C# is "much better" its far from a huge improvement.

IMO its a matter of which syntax you prefer most.

[Apoc]

i say default to the easiest, because people who learn a language specifically for the purpose of memory editing are likely to learn only a specific portion of the language and would have a much easier time with something thats simple and easy to understand even for a beginner.
this might not be the best solution programming-wise but as far as working code goes you would be better off with something easy to understand.



ok, VB supports bad programming habbits, and yes C# does have some functionality that VB doesn't, but that extra bit of functionality isn't exactly large, the differences are minor at best. and unless your counting syntax i have no idea how you can say C# is "much better" its far from a huge improvement.

IMO its a matter of which syntax you prefer most.

Yes, and the lack of any pointer arithmetic in VB doesn't help at all. (FYI: you'll need to use pointers if you ever plan to do function hooking in .NET)

Microsoft is trying incredibly hard to make C# and VB.NET interchangable. However, you dig yourself a very, very large hole by going the VB.NET route. I can't tell you how many people I've seen be completely dumbfounded when give some small snippet of C++/C# code, when they've only coded in VB(.NET). If you learned C++, you can understand C# quite easily. (Minus some minor things of course) C++/C# coders can easily read/program in VB(.NET), even though we refuse to program in it due to writing a book, rather than a program.

However, VB(.NET) people seem to have quite some issues with trying to do anything with a C based language. (I'm not saying all of you do, but those who have only programmed in BASIC languages, usually have an incredibly hard time trying to figure out what the hell is going on in C style code)

I always tell people not to learn VB if they have a choice. Learn a C based language, and you'll learn VB in the process. If you just learn VB, you'll only know VB, and have a hard time learning any C based languages.

Not to mention, programmers who know C based languages get paid more in the IT industry. (Yes, it's a fact, go look it up.)

[Karrde]

C# and VisualBasic.NET are both interpreted and compiled into the .NET CIL, and you can use them in conjunction if you were more comfortable with VB.Net, but still needed to use some of the extra C# functionality.


But if you're starting from scratch, go with C#, or even C++. Especially if you think you might ever want to be a professional developer - Fact of the matter is, C#/C++ devs make more than visual basic devs.

Edit: Apoc beat me on the salary bit!

Edit2: Also, the VB.Net compiler creates longer (And as such, less efficient) CIL code than the C# compiler, or used to. I'm not sure if this is still the case, but it likely is.

[omfgman]

ME CODEZ IN LOLCODE!

[qwjqwj]

Python is also good for RAD. Especially for high AI bot.

[typedef]

LOLCODE "ROFL" thats funny shit. If you could do some Memory Editing with that you would have one hell of a laugh. But on other note, I will learn C++ a little more, then I will check out the Assembly, it will be hard but I guess I will need it it. Cypher you should do some tutorials on some of the programs you make, well thats if you wanted. I probally wont start with Addons, thats pretty Boring. My first thing will probally be like some sort of Radar Hack. Look Foward guys, see ya in like 4 months when Im done haha.

EDIT: Well I found a Amazon Book, I might torrent it, but, is this a good book to learn the stuff I need to in Assembly, I don't wanna learn Assembly fully. Any books recommended

[Cursed]

LOLCODE "ROFL" thats funny shit. If you could do some Memory Editing with that you would have one hell of a laugh. But on other note, I will learn C++ a little more, then I will check out the Assembly, it will be hard but I guess I will need it it. Cypher you should do some tutorials on some of the programs you make, well thats if you wanted. I probally wont start with Addons, thats pretty Boring. My first thing will probally be like some sort of Radar Hack. Look Foward guys, see ya in like 4 months when Im done haha.

EDIT: Well I found a Amazon Book, I might torrent it, but, is this a good book to learn the stuff I need to in Assembly, I don't wanna learn Assembly fully. Any books recommended

Link

There are alot of good books (dunno about Assembly, but still worth checking out )