Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Max White]

moherfucker

[GlyphGryph]

@Stargrasper: I'm a firm believer in duct tape programming. I don't consider any programming practice inherently good or bad, as there are always both good and bad ways to use it. If it works, use it. If it doesn't, don't. Calling something "good" or "bad" is a sign of ignorance and close-minded refusal to accept that anything can be used both properly and improperly.

Mind you, there ARE considerations beyond "does it work" that a person can consider when thinking of something as good or bad. Other considerations:
If I look at it later, will I be able to easily follow how it works?
Does it work efficiently?
Will I be able to modify it later as requirements change?
Is it modular - will I be able to reuse when solving future problems?
Is it easy to test?
Does it have a consistent API?
Will it work on systems other than the one I built it on?

moherfucker

Mwahaha. Was that supposed to be difficult, though? Or was I not supposed to do it in Ruby?

[Mego]

I'm mainly talking about built-in features. Third-party libraries are a whole different story.

[Max White]

Trust me, things get different when more than one person is working on a project. Duct tape doesn't cut it.

[Mego]

Spoiler (click to show/hide)

Actually, it does.

[Max White]

That is what you get for not making your static methods thread safe. 

[Valid_Dark]

Finally got a triangle wave to work and was able to implement it in and it didn't work as well as the sine wave version.
I guess the sine wave version is going to work.
I really shouldn't be wasting time with gradients when I don't really have a use for it.  and I'm only on lesson 4 of my sdl tutorials.
been working on it for like 6 hours now, all sorts of different gradients and tests and stuff.  there goes most of my day wasted as I got nothing of note done.
well I started off with notes in a notebook of an algorithm I wrote last night and was able to get it fully working in SDL so it wasn't a total loss.

[Stargrasper]

Time spent learning what doesn't work is time well spent.

[SolarShado]

Finally got a triangle wave to work and was able to implement it in and it didn't work as well as the sine wave version.
I guess the sine wave version is going to work.
I really shouldn't be wasting time with gradients when I don't really have a use for it.  and I'm only on lesson 4 of my sdl tutorials.
been working on it for like 6 hours now, all sorts of different gradients and tests and stuff.  there goes most of my day wasted as I got nothing of note done.
well I started off with notes in a notebook of an algorithm I wrote last night and was able to get it fully working in SDL so it wasn't a total loss.

For gradient generation, have you tried linear interpolation? SDL might even have a ready made implementation, it's pretty commonly used in graphics.

[Valid_Dark]

I'll take another look at gradients when I finally have a use for them,
I spent the rest of the day learning to implement keypresses,
and started working on my first real game that doesn't take place in the console.
working on alpha blending right now, and tomorrow I get to tackle sprites, and by then I should have the first playable version of my first game.
it's a robot juggling game called Robo-Juggler, (a game where you are a robot who juggles, not a person who juggles robots)
it's coming along nicely.

Just figured out how to alpha blend.

[Aqizzar]

Okay, folks, riddle me this.  Take a look at this code:

Code: [Select]

if (attack > dodge)
{
if (DAM > BLK)
if (target.currentHP > DAM)
target.currentHP -= (byte)DAM;
else
if (target is MobObject)
RemoveMob(target.mobX, target.mobY);
else
if (target.currentHP > 1)
target.currentHP -= 1;
else
target.currentHP = 0;

Where all of the variables have been defined.  The Objects "attacker" and "target" are both members of a Superclass which contains both the Player and all NPCs.  "currentHP" is a variable that all members of that Superclass possess, as it is defined in the Superclass.  This method can be called by both the Player and NPCs.  In practice, it does work when an NPC calls the method and it reduces the Player's currentHP (since as of now, the NPCs only ever target the Player).  When the player calls it on NPCs, it triggers but the NPC's currentHP never changes.  Why the Hell would that happen?

[Gatleos]

Is the player a global object?

Maybe you passed a copy of the NPC in instead of the object itself.

[Nadaka]

Okay, folks, riddle me this.  Take a look at this code:

Code: [Select]

if (attack > dodge)
{
if (DAM > BLK)
if (target.currentHP > DAM)
target.currentHP -= (byte)DAM;
else
if (target is MobObject)
RemoveMob(target.mobX, target.mobY);
else
if (target.currentHP > 1)
target.currentHP -= 1;
else
target.currentHP = 0;

Where all of the variables have been defined.  The Objects "attacker" and "target" are both members of a Superclass which contains both the Player and all NPCs.  "currentHP" is a variable that all members of that Superclass possess, as it is defined in the Superclass.  This method can be called by both the Player and NPCs.  In practice, it does work when an NPC calls the method and it reduces the Player's currentHP (since as of now, the NPCs only ever target the Player).  When the player calls it on NPCs, it triggers but the NPC's currentHP never changes.  Why the Hell would that happen?

I would need to see the code for the player, npc and superclass... But i have seen issues like this when a subclass has a member with the same name as the superclass.

[Aqizzar]

I can assure you that I did not do this.  The PlayerObject and MobObject are inheritors of the SuperMob class.  I believe anyway.  Max White might see something I don't, since he has a copy of the code I'm looking at.

Is the player a global object?

Maybe you passed a copy of the NPC in instead of the object itself.

The Player is an object, a member of the same Superclass as the NPCs.  The attack method itself is part of the "map object" class.  Every NPCs is constructed with a reference value for the Player and the map object it is contained in (with a List<>).  When the NPC acts, it calls on its map's attack method, passing itself in as the (SuperMob attacker) and the player as the (SuperMob target).  When the player acts, the static program body calls the attack method from the currently-in-use map object, passing in the Player object and the referenced target, respectively.

If anything is being copied instead of called, then all my nightmares about Object references are coming true.

[Max White]

Hold on, code diving now. Let's see what we can bring up.