/prog/ - Programming

>Comes to a board about programming

>Asks programming question

>If this isn't the right place to ask I'll delete my post,

??? where else would you ask about programming? /furry/?

Wish I could help but i'm in the same spot as you mate. There's always cancertube to learn about some things. Wouldn't recommend it really though.

>>3814

I prefer textbooks to youtube, to be honest. I hate informal instruction and I like the in-depth explanation that details what each jargon word means. It may be slower but complete knowledge is more useful.

I can already see classes and methods taking shape as RPG databases for calculations and NPC data storage.

Question for the pros: am I correct that each 'entity' in a game, such as individual enemies, will be objects that are instances of classes, and that things such as combat and dialogue could be handled through methods contained in different classes?

If you're a total beginner, start with Python and especially the Pygame library. The clean syntax, minimal boilerplate, and strong library support will allow you to stay motivated longer and thereby make more progress.

For a textbook, try something like "Invent Your Own Computer Games with Python": http://inventwithpython.com/chapters/

It covers all of the basics and teaches you all that you need to make simple games.

Python can take you pretty far, the only real issue with it is performance. By the time Python's lack of performance becomes an issue for you, you'll most likely have several completed projects already and will have a strong grasp of the big picture of video game design. You can move to a more performant language like C++ or C, and the transition will be fairly smooth.

I don't want to discourage you, but your programming skills are irrelevant if you want to "make games" because of existence of various game engines. It's 2016 and even AAA-tier engines are now free for general public. If you want to make a game like Sengoku Rance, you should first learn how to draw good looking 2d porn, not how to program. That comes later.

Learning to program is a good way score a decent job though. Java is very popular in enterprise desktop segment, if you'll git gud at it you'll probably have a decent chance of getting a job.

>>3813

If you're serious about making games, I'd recommend learning C++ and maybe some library like SFML. However, as long as your game is simple enough, Java (or other similarly not-so-efficient languages) might do the trick.

>>3817

>your programming skills are irrelevant if you want to "make games" because of existence of various game engines

What are you going to do with that AAA-tier engine if you can't program?

>>3818

>What are you going to do with that AAA-tier engine if you can't program?

You learn language specific for your tool of choice on a level good enough to write down game logic. Which isn't even obligatory, for example, with UE Blueprints, which is basically a visual drag-n-drop scripting tool. It's still programming, but it's much, much easier than writing something in C++ from scratch and is more time-efficient.

And even if you bother writing something from scratch, if you have "programmer" graphics no one is going to play your game.

>>3813

You're confused.

>I want to learn how to program so I can get a job programming

>But I want to program so that I can make a stupid indie game.

>What language do I learn?

Ask yourself:

+ If I am going to be an indie developer, where will I get the funds to support myself while I am creating the game?

+ If I am going to be a programmer, where do I see myself being employed?

Your post clogs up this board because everyone has a different idea of what you're trying to work towards. Delete the thread and ask a more specific question.

>>3821

You're right, there is a lot of information out there and I suppose I was drunk when making the post.

My main question is - I'm learning Java, so what else should I be doing to get a job in the field? The game development thing is more of a hobby and something I'm doing on my own time, I already have a real job, though I dislike it.

>>3822

Learn how to design and use databases, and create database applications - most jobs are going to be database applications.

This includes:

SQL

ER Diagrams

Normalization

Since you're working with Java, learn how to use Hibernate. I hate ORMs because there's too much abstraction, but they're somewhat popular.

When you're comfortable with Java, learn C# - it's very similar, so it should be easy, but it's far more polished and has a lot more convenience features. Like Java, there are a lot of jobs in it. Learn to make database applications using winforms. Bonus points for WPF. Do a project using NHibernate for good measure.

>>3824

>Learn how to design and use databases

These are good bonus skills but there's such thing as DBA staff

>>3822

There's some development related stuff like version control, continuous integration and testing, you probably won't read about those in general books on Java. You're probably not expected to be familiar with those as a junior, but then again, those are good bonus skills. And unlike databases, those 100% will be useful.

>>3825

Most of the time, I've been expected to make the whole application. That includes designing the database.

Gotta agree on version control, though.

>>3824

>>3825

All right, I'm saving those posts even though I don't yet know what most of the acronyms stand for. It seems that some research is in order.

Thanks guys.