Search Results
Searched for posts by capristo in all forums

Showing results 591 - 600 out of 1651 total
Modify your search
Posted by capristo, Jul 27, 2014 at 2:45 pm
Sweet, congrats! I should tame more, I usually don't because I feel like they just get in your way.
Posted by capristo, Jul 13, 2014 at 10:35 am
Right.

If you're one of the 5 current admins, stay within the Attnam/ivan repository
- push directly into master for small bug fixes
- create your own branch and merge it in for large changes

If you're not, fork the repository and then submit pull requests to the master branch that one of the admins can approve
Posted by capristo, Jul 10, 2014 at 2:29 am
I should note that this doesn't apply to Pent or Warheck. More for people who want to make minor contributions such as bug fixes, or add their own features/ideas that haven't necessarily been agreed upon for the official release
Posted by capristo, Jul 10, 2014 at 12:29 am
I was going about this the wrong way by adding every contributor to the Attnam organization. I trust everyone who's in there now, but what contributors should really be doing is forking the repo and submitting pull requests with their contributions.


Create a Github.com account. Go to our repository:

https://github.com/Attnam/ivan

In the top right, click "Fork" to create your own copy of the code.

If your username is "frodo", for example, you will now have your own fork at

https://github.com/frodo/ivan

You can then "Clone" that repository onto your local computer. Edit the code locally, make any changes, then "Commit" and finally "Push" back to the master branch of your fork. For Windows, I recommend TortoiseGIT

For *nix systems:
git clone https://github.com/frodo/ivan.git

# Check for modified files:
git ls-files -m

# Check for new files:
git ls-files -o

# For each modified or new file (or folder, this command is recursive)
git add filename

# After all files have been added, check status again to make sure. Should output nothing
git ls-files -m
git ls-files -o

# Now commit and push
git commit -m 'Description of changes'

git push origin master

Then back on Github, go back to your fork link.

On the top left is a green button to create a "pull request." When you create a pull request you're basically saying "I made some changes on my own fork, and I'd like you to review them and merge them into the original repository"

Then one of us will approve or deny the pull request.

I'll add more detail later..
Posted by capristo, Jul 3, 2014 at 1:12 pm
Oh man, perma slowed would SUCK
Posted by capristo, Jul 2, 2014 at 9:26 pm
I vote to keep it.
Posted by capristo, Jun 13, 2014 at 1:16 pm
I don't like that the other monsters are removed. Corpses have their use as food too, besides, I've never seen the entire level wiped out before I was able to kill the Enner.

But aside from that i really love the river idea as well. How wide is the river? If it were 3 or 4 spaces that might even help because if you saw the Enner across the river you could zap him without him being able to get too close to you.

If you can get the river working I would be fine with that in 0.51 but I think the monsters should go back. Just my opinion
Posted by capristo, Jun 12, 2014 at 4:38 pm
Haha that sounds awesome. Looking forward to the screenshots
Posted by capristo, Jun 5, 2014 at 2:26 pm
Shouldn't bashing be based on your body weight? When I hear the word I picture somebody throwing their entire body up against a door
Posted by capristo, Jun 2, 2014 at 11:11 am
Haha that was pretty epic though.

I've definitely had some characters like that. Doomed to failure from the very beginning but you somehow keep pressing on. And then when they finally die you're like "I should have just quit a long time ago"