Crysp 님이 먼저 게시:

Reaper 님이 먼저 게시:

Not to mention I can walk out into the void (black area with no ground)

Your absolutely right about that. In the comming update there won't be black areas. I the future we'll make storyline.

thank you for checking out the game!

No worries, the concept of it looks awesome

Not to mention I can walk out into the void (black area with no ground)

The world generation style is awesome. Just clueless on what to do other than chop wood and guess what to craft

epicmars 님이 먼저 게시:

Reaper 님이 먼저 게시:

I took the liberty of making a Discord channel for this Steam group. It is a more versatile way to do exactly what we are doing here. It has all the perks of voice/text chat and acts as a meeting ground for a great community. There is a desktop app, browser app and mobile app so you can use it whenever and whereever. https://discord.gg/0118J0cTzDut6TTmQ

Thanks for taking the time to create something to improve this community.
I added it to the front page.
If you want to change the texts I added on the front page then message me or comment it as a reply in this discussion

No problem at all! The Steam Group is great but its a lot less customizable than Discord and I feel that it would be a lot more user friendly once you get used to it. Give the group more of a community feel than a forum.

I took the liberty of making a Discord channel for this Steam group. It is a more versatile way to do exactly what we are doing here. It has all the perks of voice/text chat and acts as a meeting ground for a great community. There is a desktop app, browser app and mobile app so you can use it whenever and whereever. https://discord.gg/0118J0cTzDut6TTmQ

ZaMi (inDev) 님이 먼저 게시:

i have not denied so whats ur prob?

I have no problem friend, happy coding

ZaMi (inDev) 님이 먼저 게시:

i dont like to work with alarms so i use delta_time or current_time, DemiGoth was right ! never use a counter as timer (if ur pc do lag, the counter will too) use delta_time or current_time this wont have this problem (excuse the german/english :P)

Just going off of your original subject of low script basics, alarms are the easiest way I can think of to do what you are wanting

I am currently working on an arena based tank game and I for the life of me can not figure out how to work out an aggro range. I want the tanks to path to a player but not get so close that it pushes the player out of the screen/room. How would I go about doing this?

reference code:
image_angle = point_direction(x, y, obj_player.x, obj_player.y);
mp_potential_step(obj_player.x + 15, obj_player.y +15, moveSpeed, true);

Albcatmastercat 님이 먼저 게시:

Reaper 님이 먼저 게시:

I think I mostly get the idea and most of the syntax with GM:S it's just understanding where and how to apply them so they are efficient. The game was made on a whim and if an actual programmer saw the code and how unorganised it was, they would probably faint. For any future projects I will write my ideas down and organise my thoughts more clearly before I begin haha

Ok :P
But remember, larger projects would probably require more than what GM offers.
For instance, I was thinking about making an RPG, with evolutions and many kinds of abilities. Thing is, I have -no- idea how to make an inventory and save system :s

GM is very capable of anything I have to throw at it. If you have ever take a trip over to the YoYo games showcase you would understand. There are plenty of ways to go about making inventory and save systems in GM and you are very much able to do so. Youtube is your best friend and when Youtube fails Google is a great backup. I literaly learned everything I know about programming from those two resources.

Albcatmastercat 님이 먼저 게시:

Reaper 님이 먼저 게시:

As I posted in the other introduction forum I am fairly new. I think I only have 1 global variable in use but I can not for the life of me remember what it is. When my PC, which is what I use for programming, is back on line I will be able to refer to it. But for now the game is entirely all too simple.

Ah, I see.
I can help with -that- itself, as I have a faint sample of knowledge on those.

I think I mostly get the idea and most of the syntax with GM:S it's just understanding where and how to apply them so they are efficient. The game was made on a whim and if an actual programmer saw the code and how unorganised it was, they would probably faint. For any future projects I will write my ideas down and organise my thoughts more clearly before I begin haha