#coding problems

[anne-the-historian-ish]

*shakes my html and css code*

WHY DON'T YOU JUST SHOW THE VIDEO? LET ME PUT MULTIPLE VIDEOS JUST LET ME SHOW THE FUCKING VIDEOS JUS-

[mindymortondev]

Trigger Zones and Parallax Hell

If only you knew the pain I've been going through with cameras in Game Maker Studio for the past few weeks! But it's fine, I've got it all figured out now. This post is going to be a pretty long one. To be honest, there are a lot of little things I've done since the last post that I'm just going to either gloss over or save for a different post (maybe?) Primarily trying to standardize my code, resizing my sprites again, and hitbox thingzzz.

Anyways let's get into CAMERAS!

So game cameras were a little bit of an enigma for me going into this. From application surfaces to resolution, to window size... Quite frankly, they're very powerful tools when it comes to building a game, and all the stuff you can control with GameMaker's camera was frankly-

a massive headache.

Come down the rabbit hole with me-

TRIGGER ZONES

First things first, I had to get the camera set up. There are a lot of tutorials on this, all of which are slightly different. My code ended up somewhere in the middle of all of them. Here was the first tutorial I followed:

How to make a Camera for any GameMaker game in 4 minutes by Shaun Spalding

So Shaun Spaulding's video helped me get the camera set up in the first place, although frankly, this method didn't last very long in my project. It was good and simple but for whatever reason, people really don't recommend you use GameMaker Studio's Room Builder's camera settings, but rather code them yourself. I'm not sure why else other than the fact you get a lot more control over your game's in-game camera, resolution, and window size, plus you can create cutscenes and stuff with it. Next was-

Smooth Camera Tutorial + Pan/Zoom [GameMaker Studio 2] by Matharoo

Matharoo's code was more complicated at first but it gives you that level of control that I was just talking about, and it sets it up in mostly the same way. Although, my code now is definitely a mash-up of the two tutorials.

With those two tutorials, now our camera looks like this:

This is great! Now we have an actual camera instead of looking at the whole room! But if we look at our camera's view, we can see that the camera is seeing out of bounds. Matharoo's video may have actually covered this (you can watch it yourself) but where I found my solution was-

Camera Modes | GameMaker Studio 2 by FriendlyCosmonaut (this one starts at 14:33)

I did not watch this entire video but it looks like it has a lot of useful information in it. Even though she isn't making the same type of game in the video, she does cover the topic I needed, which the provided link will actually jump straight to that section of the video

This is solid! Now that we have one problem solved, it's time for another-

Unless you're going for something more old-school like Super Metroid, we're likely going to have big open rooms that twist in multiple directions. I had a pretty clear vision of how I wanted the camera to operate. My trajectory is in the direction of Hollow Knight, which has a simple yet complex camera system that is very well explained in this YouTube video:

This video sort of became my "mission statement" with all this. Unfortunately, I don't have a tutorial I can point to for how I coded all the stuff in this video, but I did realize Shaun Spalding briefly touched on his own solution to this kind of problem with what he called "trigger zones". This is a good way to describe my own solution. Essentially we're going to create an array of overlay objects, or "trigger zones" that will restrict the camera's movement to only being able to move where they say. This is more or less the setup we're looking at:

This is how Hollow Knight's cameras appear to be working in the video, and how we'll set them up too. I won't dive too deep into the nitty-gritty coding on this one, but basically, each of these trigger zones is an object in GameMaker that will bind the camera by their respective dimensions.

This gets very inter-relational with all these objects since each object needs to be able to apply its own unique dimensions to the camera boundaries. It did become a little bit of a headache managing what turned into 5 or 6 different camera-related objects which were all modifying each other.

Here are some pictures of how this looks in practice. Keep in mind that these would all be turned on at once to function properly:

Vertical Trigger Zones (the camera won't move above or below the zone the player is in)

Horizontal Trigger Zones (the camera won't move too far left or right in these zones)

Zoom-In (or Zoom-Out) Zone (the camera will zoom in/out as far/close as the width of this zone)

These are just a few examples but hopefully, the concept makes some sense to you! So finally, with these systems in place, our cameras will finally move like this:

And that is (mostly) the end of that. Scope creep has kept me coming back and adding incremental changes to all these features (specifically the zoom one). Fundamentally they will continue to work the same but it's easy to keep tuning things like camera speed and zoom speed.

Anyways, with this stuff done it's time to get to the next thing:

PARALLAX HELL

So the actual solution to this was straightforward--use a 3D camera and follow this tutorial:

From 2D to 2.5D: GameMaker Studio 2 TUTORIAL (Using 3D Camera) | Easy Parallax by Matharoo

It's what Hallow Knight does, it creates a natural parallax effect, and it makes a lot of the artistic work pretty easy. But, the reason it took me so long to get here is a story that brings me great pain...

To start, I wasn't originally going to use a 3D camera because they sounded somewhat complicated. Even Shaun Spaulding sounded like he didn't recommend them in his tutorial that I shared above (although maybe that's just for beginners). What I was going to do could be called "interpolated parallax," where we are basically moving a bunch of image layers around relative to the position of the camera.

You can learn more about this in this video by Pixelated Pope.

That doesn't really need to make sense to you, but that's what I was doing. Now, this method could have totally worked theoretically if it weren't for the fact that GameMaker Studio 2 has actually removed certain coding properties from GameMaker 1.4, which makes this method kinda unreasonably difficult? At least from what I tested. It works great if your only intention is to have an endless runner game or if you want to accommodate for open space by drawing individual sections of background together in a giant 4k+ canvas.

It sounded messy and I didn't really want to deal with it. Eventually, I learned more and more about GameMaker Studio's 3D camera, which was easy to set up for my specific needs.

It did take a while to fine-tune it all but I did get there in the end. It did, however, break my zooming trigger zone. This post is already long enough but basically, I thought the solution would be needing to change the camera's field of view with trigonometry when it was actually just changing the camera's distance with a basic ratio...

Not my brightest moment there and it took a painful couple of hours of staring at the same code and Desmos to figure that out.

ANYWAYS...

The camera system is finished! Or at least, finished enough that I can move on to designing backgrounds, and just fine-tune this bit by bit later down the line.

Honestly, this was all very time-consuming, and the struggles with the zooming trigger zone were a bit demoralizing, so I'm ready to get back into the art generation side of things!

I also plan to spend some time beating Hallow Knight and maybe a few other platformers I can take reference from for backgrounds 😎

See you next time, everyone!

[writingwithcolor]

Indian-coded character feels like outsider because of sandy hair and eyes

@frauastra submitted:

hello! my fantasy novel is set in a country which is a hybrid between ancient egypt and india, so all of the characters are fully black or indian-coded with the exception of this one. he is mixed (norse and indian), so he sticks out a bit due to his appearance (he’s described as having ‘sand-colored’ hair and eyes, for instance) and family background. i feel like this might have some unfortunate implications at first glance, but i’m not sure. i wanted to describe him as feeling disoriented and outcast from the majority; his trying to find where he belongs is his main character arc as well. would it come off badly?

What does India-Coded Mean?

I’m always wary when someone says India-coded, as this tells me they don’t know much about the diversity in India or the subcontinent as a whole. Have you seen the ethnic diversity in India? One of the reasons we haven’t yet written a South Asian Ethnicity resource post is because the India section alone would take forever.  (This is not to say that other countries in the region are not similarly diverse, but most South Asian ethnic groups are represented within India in some capacity.) 

If this character is from Kashmir, he could very well look like your description even without the caveat of being mixed because to be South Asian often is to be mixed by default. If this is a fantasy world, what does being “Norse” mean in this context? How did his parents meet? Ancient Egypt and Ancient India had long, complex histories, so please consider the time periods you are drawing from.  In general, it sounds like you need to do more research and also to trace your logic about your approach to world-building.

Issues with Outcast Status

Why does this character feel like an outcast from his group? I’m going to give you the benefit of the the doubt that you couldn’t possibly be thinking of writing a reverse racism type story. Again, most people in India are of mixed descent. I highly doubt the character’s racial heritage would be a factor in feeling out of place. You had better come up with something more compelling in his backstory or characterization to explain this internal struggle.

- Marika.

To add to Marika’s notes, I’d like to double down on being extra careful you don’t veer anywhere near a reverse racism theme. If he’s the main character in a fantasy novel, be wary of any inadvertent “white savior” tropes here too (or in this case, a “light-skinned savior” trope).

Also, it’s been a while since I’ve done any deep Ancient Egyptian deep dives, but if I recall correctly, they had quite a substantial pan-Meditteranean trading setup, trading with a variety of different cultures and peoples. In a fantasy world, I don’t think it would be unreasonable if this was similar or even more common--why, exactly, would a mixed-race paler character feel so deeply out of place? I would advise writing with care, and definitely double down on researching Ancient Egyptian and Ancient Indian cultural diversity.

--Sophia

[scaleracademy]

To be a great software engineer, you need the following skills:

Good at Problem Solving

Ability to build a tech system from a real-world problem

Scaler Academy's curriculum has been formulated keeping the above requirement in mind. To ensure that each learner gets thorough knowledge of Computer Science fundamentals, and attains specialisation in backend or full-stack while gaining proficiency in System Design (High-Level Design and Low-Level Design) through a project. Our batches are categorised basis on their proficiency: Beginner, Intermediate and Advanced.

Experience Scaler Academy with our Free Trial:  https://www.scaler.com/academy/

Scaler Academy Review: https://www.interviewbit.com/scaler-academy-review

[programmingbeast]

05 Ways To Kill Your Procrastination As A Programmer!

👉Programming Hero - https://onelink.to/proghero9

If you want to learn Python, then download the app called 'Programming Hero' and start learning and practicing from the same app for free initially. Don't miss the chance of getting help from the free forum inside the app too.

[cogscibi]

Ahhh i accidently deleted all my java programs 😭😭

Also still don't know how to install python

[sciencefordragons]

So this photometry code I use does iterative sigma clipping, but for some of the galaxies the code crashes because the masked array isn’t being created, so it just creates an empty numpy array instead. And since the array is empty, it’s iterating over nothing.

Returns this error: numpy.ndarray object has no attribute mask

I had this problem before when I was trying to use this code, and the scientist who wrote it speculated that it was because the galaxies were too faint, but this is happening for objects like M101 and M82, which are very bright galaxies.

Now that two of us have had this problem, we gotta bother the scientist.

[timlncomic]

Not shown: 50+ hours of the code NOT working

(also this exact thing happened again 30 minutes after i finished drawing this...)