Garan

It's really the same thing as several raycasts, just a lot easier to calculate.

The kind I described above, with a mapping to a radial map and then a flood to figure out what's blocked.

The propagation seems like it could be hard to do, though

The issue then is a moving lightsource.

You might also be able to do a mostly baked lighting- cache it and only update if a tile has been changed.

I see. Can you increase the brightness of a tile to turn it into a lamp of sorts?

When it hits something that filters the light, continue flooding with that filter to the rest of the column

Then, fill from the top

(so that the top is the closest to the light source)

Then, map that from Cartesian to Polar coordinates

For each lightsource, render everything it might hit to an occlusion map

So you might be able to do that with what I had in mind

At some point I might come back to the 2D lighting engine I was trying to make.

(assuming you're using OpenGL)

@WilliamMariager This might help: khronos.org/opengl/wiki/Image_Format

I seem to recall the ability to set two channels each for RGBA in OpenGL but I'd have to find where I saw that.

I think there are more available, yes.

Too often I see bloated structures where everything relates to everything else in this giant tree of inheritance.

I find that ECS itself is often not the right thing, but the reason for it over OOP is very valid. Subdividing classes into more modular components is important.

There have been times when I've had the drive to do /something/, but without a target for that.

I know that feeling

I'm stuck in a loop of "this is definitely the project I'm going to be able to focus on for a long time and maybe even finish at some point" and "ooh, this would be a cool idea for a new project!"

I know that feeling.

To parse what he said: you go 'join my server' but don't actually tell us anything about that server.

Same. I don't use Discord normally.

It's another to show the player "this is the sort of change increasing your strength will have" by demonstrating a high strength vs. a low strength.

It's one thing to say "Strength makes you do more damage".

Something I just thought of about character generation in RPGs: Presenting players with skills without demonstrating what those skills do is pretty bad design.

But Unity doesn't play nice with that in the inspector.

The easy way to do this would seem to be a dictionary with strings as the keys and GameObjects as the values.

And also not have it be as bad as doing an instantiation from a non-loaded prefab (one that's not referenced in any script).

I want to be able to instantiate prefabs via a lookup from a string.

I'm having a bit of a conundrum:

So everything has a "use with" function, but only the Key will check if the target is a door and if it is, will open the door.

I feel like your best bet would be interfaces rather than classes. You can mix those, but the key here is ensuring that your components have a definition for things even if that definition is defined as "do nothing".

@Jimmy What you'd probably then want is an "on hit" object that is called whenever the weapon deals damage. Most might have an empty class for that but the ones that set things on fire have an object that applies the "on fire" status to what was hit.

Or, you use a long list of flags a given item has.

@genaray Then at the very least you'll need a different class for each.

If the only difference between skeleton and stronger skeleton is the values of their stats, why not just have different values for stats?

@genaray How are you going to make different functionalities without different classes?

@doppelgreener -_-

Good. It's been way too humid.

Hey, I too am lazy and wanted a fast solution.

bfy.tw/JDWF

Is this server-client based or peer-to-peer (I don't know but this will help find one)

o/

Oops

o?

There's something to be said for knowing EXACTLY what your language will and won't do. So you know that if you're shooting yourself in the foot, you know exactly how and why.

*would be relevant to me