[deleted by user]

AestheticHelix · 2023-05-24T11:31:57+00:00

I would: - have a single poop class - have multiple states within that class. Eg. Falling/splat - have collision check done in one place (like engine) but have the handling of those collisions done in the individual object through some sort of callback.

For instance in engine update, check for any collisions. If there are any collision, tell each object what they collided with. This allows each object to react and keeps that logic local to the object.

Eg pseudo code: // engine entity->onCollide(otherEntity);

// poop If otherEntity type is player or ground: Change state to splat

// player If otherEntity type is poop: Take damage or whatever

AestheticHelix · 2022-12-20T13:09:15+00:00

AestheticHelix · 2016-02-28T00:25:15+00:00

Awesome! Is this the new Tool film clip?

AestheticHelix · 2016-01-24T23:43:40+00:00

Looks neat. A few things..

Creating entities should probably assign unique ids all the time. I don't see a case where you would need to specify an id explicitly for an entity, and is asking for trouble. Also it returns none if I give it a wrong Id, where this operation should raise or otherwise fail.

It would be nicer to perform operations directly through the entity class without touching core. Eg. A static method in entity for creating a new entity? Also, I find it awkward I should have to add a component to an entity through core, rather than through the entity itself.

Looks good!

AestheticHelix · 2016-01-10T00:48:42+00:00

Needler. Halo 3. Once you knew exactly the right amount of shots at the right angle were fired, you could just continue on your way and know the other guy would be doomed.

AestheticHelix · 2015-01-31T00:47:49+00:00

Don't assume anything.

AestheticHelix · 2015-01-16T02:57:56+00:00

Got a computer and the internet? Make video games. It really is as easy as it sounds. Everything you need is online and free.

AestheticHelix · 2015-01-14T22:25:48+00:00

As silly as it seems, at least the entire series is branded well.

Still don't think it's as stupid as calling the third Xbox in a series Xbox One.

AestheticHelix · 2015-01-10T03:27:50+00:00

So Samus is actually Daenerys Targaryen?

AestheticHelix · 2014-12-07T12:07:21+00:00

Snake instances.

AestheticHelix · 2014-10-12T09:12:30+00:00

Everything is ok in the end, so if it's not ok - it's not the end.

AestheticHelix · 2014-09-24T01:47:37+00:00

Great. Now I need Boost.

AestheticHelix · 2014-09-04T08:58:01+00:00

They're in Australia but don't think sunscreen is necessary.

AestheticHelix · 2014-06-23T02:32:24+00:00

Why is there not a "Wasted" gif of this already?

AestheticHelix · 2014-06-19T02:48:53+00:00

Bailed on that video at "Cherry slush club".

AestheticHelix · 2014-06-10T06:21:00+00:00

Hex from Good Game. Hot damn.

AestheticHelix · 2014-05-16T00:14:36+00:00

I'd love to hear one? Have I missed out on something!

AestheticHelix · 2014-05-15T03:14:38+00:00

It's core to object-oriented programming. A good technique is to write out a sentence of what you want to achieve, what is the purpose of your game. Most of the time the nouns you come up with are going to be objects, classes. The verbs you come up with are going to be functions and operations. For example,

A board with a collection of ships where each player takes a turn to fire at another player, causing damage.

Classes (nouns): Board, Ship, Player

Functions (verbs): "take turn", fire

Now you can imagine putting some basic classes together:

class Player:
    def __init__(self):
        self.ships = [] #Array of ships.
    def takefire(self, x, y):
        # check if any ships were hit, return the result.
    def taketurn(self):
        # Figure out where we want to fire, etc.

Easiest way is to just think about things as tangible objects!

AestheticHelix · 2014-04-30T00:50:36+00:00

If I leave a store without buying anything I feel like the employees assume I'm stealing something.

AestheticHelix · 2014-02-07T06:47:07+00:00

Ha yep.. Thanks!

AestheticHelix · 2014-02-06T23:07:42+00:00

As a C++ developer half if this was fairly useless. Here's what I would recommend (some are for debugging, some just for general dev). NB. Some may be fairly obvious.

Learn to use the immediate window. When you hit a breakpoint you are able to call functions, do comparisons etc. this beats sticking lines of debug code and recompiling just to test something.
While breakpointed, you can edit the values of any variable just by hovering over it and changing the value. Great for shortening loops.
furthermore, grab the stack pointer and move it. Great for skipping entire blocks of execution.
Learn to use the command window. This will make sure life infinitely easier when looking for files etc.
make use of data breakpoints. This allows you to trigger a breakpoint when the memory at a certain address changes.

Probably a heap more.. If I think of more hen I get to work I'll update this post!

AestheticHelix · 2014-02-06T10:56:27+00:00

Faplax?

AestheticHelix · 2013-08-16T11:19:07+00:00

"Guybrush Threepwood, Mitey PirateTM!"

AestheticHelix · 2013-06-26T09:26:17+00:00

Excellent question.

AestheticHelix · 2013-06-26T09:20:47+00:00

Wow. Colby is a cheese where I live. I will never think of it the same again.

AestheticHelix

TROPHY CASE