Author Topic: Zombies are People, Too  (Read 18240 times)

You could add:

Creating an option to set lives.

Why is the repo closed anyway?
Just let people fork and send pull requests and the whole "application" problem goes away.

Please optimize the AI aswell so there can be more zombies with better performance

Why is the repo closed anyway?
Just let people fork and send pull requests and the whole "application" problem goes away.
I'm making massive changes that are unstable at the moment.


Please optimize the AI aswell so there can be more zombies with better performance
It's on the list.

I'm making massive changes that are unstable at the moment.
So it'll be opened publicly after that?

So it'll be opened publicly after that?
That's the idea, yes, unless I start making changes to the GUI.

That's the idea, yes, unless I start making changes to the GUI.
Maybe have a public "stable" repo and then a branch or private fork for doing stuff like this?

Maybe have a public "stable" repo and then a branch or private fork for doing stuff like this?
I don't know how to do that....

I don't know how to do that....
To create a named branch, just execute the following
Code: [Select]
hg branch unstable
hg commit -m "Added branch unstable"
hg push -f
hg branch sets the branch name of the working directory, the -f argument to hg push means that it should push even if it would create an extra head on the server (default is to bail). Switching between them is done by "hg update default" and "hg update unstable".
To create a private fork, simply click the fork button on the repo and select private. Then add it to [paths] (either do this by with the diskette button in the "sync" view of TortoiseHG or by modifying .hg/hgrc manually.

I am so glad to see that you are still working on this! I sent you a list of suggestions a very long time ago. I'll dig up the PM if you still want to see it.
And I'd be happy to make that tank model for you.

You can have the main branch, then have branches coming off of that. Usually when contributing to a more-than-2-person-project, a separate branch is used, and when whatever on that branch is stable, it is merged into the main branch, which is usually what the public has access to.

You can have the main branch, then have branches coming off of that. Usually when contributing to a more-than-2-person-project, a separate branch is used, and when whatever on that branch is stable, it is merged into the main branch, which is usually what the public has access to.
How that stuff works depends from project to project. Also each client repo and fork is, technically, it's own branch.

I fixed the issue with loading spawns and stuff.

Were there any other issues anyone can think of?

I fixed the issue with loading spawns and stuff.

Were there any other issues anyone can think of?

The only issue I remember was the "Tank" mutation not working correctly.

so thats what ZAPT stands for................ now it all make sens....e