Print

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

[Orpheon]

Great. Would you guys like to leave it open as a community thing, or would you like to put this somewhere and organize tasks as a team?

I think we'll leave it open atm.

If you have wishes of something particular you want to do, just say it an do it.

I don't think a core team is necessary yet, we are so few. Those who ever looked at the source are probably inside the core team 


Priority now is probably the collision response, but don't go and do big stuff until I upload what I already have done.

If you absolutely want to, here are the functions you could use:

Code: [Select]

functions.place_free(x, y, wallmask)Obvious, checks whether a point is free in the wallmask.

Code: [Select]

objectCheckCollision(character, wallmask)Checks whether that object hits the wallmask somewhere.


Actually, I've already improved it a bit compared to what I just posted before, and I'm almost done with getting a git repos ready.
I'll upload everything as soon as I get home.

[Orpheon]

Git Repository

Go and fork it, and then go work on the collision response (the second script in collision.py; characterHitObstacle()).

[pandaturds]

This looks awesome.

[Orpheon]

Also, I got this:

My own collision code; written from scratch.

It works somewhat better than the ported gg2 one, and it's a great deal cleaner, but it doesn't even pretend to support stairs yet and is also quite buggy.

At least it's concept is simple.

Screenies:

Of course, you don't see how the collision engine is going, you're gonna have to try it out first

[Flaw]

I'll probably work primarily on gameplay most (sentry logic, weapons, kills, round management, etc). Networking isn't exactly my field.

OFF TOPIC: Today, as a Rifleman, I shot an enemy Rifleman the instant they shot me.

Flaw (sniper) The End [be]
The End [be] (sniper) Flaw

[Orpheon]

I'll probably work primarily on gameplay most (sentry logic, weapons, kills, round management, etc). Networking isn't exactly my field.

OFF TOPIC: Today, as a Rifleman, I shot an enemy Rifleman the instant they shot me.

Flaw (sniper) The End [be]
The End [be] (sniper) Flaw

Ok. Nice idea, because those things are tedious.
Still need to get that blasted collision code working.
Also, update to that code.

[Psychopath]

OFF TOPIC: Today, as a Rifleman, I shot an enemy Rifleman the instant they shot me.

Flaw (sniper) The End [be]
The End [be] (sniper) Flaw

This happens because the hitscan code is called in the step and death script is called in the end step. Because of order of operation of those events, it is possible for two people to kill one another with any weapon; it happens with Rifles, Autoguns, Knives, explosives and every projectile. If we changed it to run the death script immediately after damage is dealt (I don't think you'd want to do that unless you just called a script that dealt damage that would in turn call the death script if the victim's health is low enough), that could work. Although it'd be a bit of a headache to redo, but hey, this is a rewrite, it can be done that way from the ground up if need be.

[Flaw]

OFF TOPIC: Today, as a Rifleman, I shot an enemy Rifleman the instant they shot me.

Flaw (sniper) The End [be]
The End [be] (sniper) Flaw

This happens because the hitscan code is called in the step and death script is called in the end step. Because of order of operation of those events, it is possible for two people to kill one another with any weapon; it happens with Rifles, Autoguns, Knives, explosives and every projectile. If we changed it to run the death script immediately after damage is dealt (I don't think you'd want to do that unless you just called a script that dealt damage that would in turn call the death script if the victim's health is low enough), that could work. Although it'd be a bit of a headache to redo, but hey, this is a rewrite, it can be done that way from the ground up if need be.

Okay.

Also, for this system, I recommend that we use a more method-based way of handling health and death.
More precisely, there's a .damage function on Character objects that can be called to inflict damage. Arguments could be amount, source and type, for example. That function would take care of subtracting health and other stuff. Then, it would also check if health was <= 0, then it would proceed to call the .kill, .onDeath, or .death (dunno about name) function which would take care of transmitting the death, removing player object, giving points, etc.

[Psychopath]

OFF TOPIC: Today, as a Rifleman, I shot an enemy Rifleman the instant they shot me.

Flaw (sniper) The End [be]
The End [be] (sniper) Flaw

This happens because the hitscan code is called in the step and death script is called in the end step. Because of order of operation of those events, it is possible for two people to kill one another with any weapon; it happens with Rifles, Autoguns, Knives, explosives and every projectile. If we changed it to run the death script immediately after damage is dealt (I don't think you'd want to do that unless you just called a script that dealt damage that would in turn call the death script if the victim's health is low enough), that could work. Although it'd be a bit of a headache to redo, but hey, this is a rewrite, it can be done that way from the ground up if need be.

Okay.

Also, for this system, I recommend that we use a more method-based way of handling health and death.
More precisely, there's a .damage function on Character objects that can be called to inflict damage. Arguments could be amount, source and type, for example. That function would take care of subtracting health and other stuff. Then, it would also check if health was <= 0, then it would proceed to call the .kill, .onDeath, or .death (dunno about name) function which would take care of transmitting the death, removing player object, giving points, etc.

Don't forget the person dealing the damage in that too or we'd just have what people died to and not who. Also, kill assist tracking would go in there. It's not that complex, just tedious.

[Flaw]

Don't forget the person dealing the damage in that too or we'd just have what people died to and not who. Also, kill assist tracking would go in there. It's not that complex, just tedious.

Arguments could be amount, source and type, for example
source; origin of the damage (what is dealing it)

[Flaw]

don't forget the person dealing the damage

Arguments could be amount, source and type, for example

source; origin of the damage (what is dealing it)

[notajf]

By the way,

for this project, I'd like it if GG2's event system was more asynchronous. We have the wonderful Twisted asynchronous networking here, why not asynchronous in-game events? Should we even keep the current step system? Although it would be quicker to copy the current design, a better, non-framerate-limited design might be a better idea.

[Psychopath]

don't forget the person dealing the damage

Arguments could be amount, source and type, for example

source; origin of the damage (what is dealing it)

What: a weapon

There is no guarantee that the weapon exists in memory when the damage is dealt.

Who: the person using the weapon

Because it is based upon the player ID and not their physical presence, this will always work unless they leave the server before the damage is dealt. In that case, default to a constant that represents an invalid player but won't register as an error.

[Flaw]

don't forget the person dealing the damage

Arguments could be amount, source and type, for example

source; origin of the damage (what is dealing it)

What: a weapon

There is no guarantee that the weapon exists in memory when the damage is dealt.

Who: the person using the weapon

Because it is based upon the player ID and not their physical presence, this will always work unless they leave the server before the damage is dealt. In that case, default to a constant that represents an invalid player but won't register as an error.

The initial origin of the damage is the player.

[Psychopath]

The initial origin of the damage is the player.

This is why you don't call people "what."

People are "who."