The future of Oangband?

[CJNyfalt]

So, I am back, and I am up for some tinkering with the Oangband code.
I am naturally asking if someone is interested receiving patches for it? Or, should I just keep my changes local?
I am not interested in maintaining it, but if people are up for a team-based approach then I am interested.

[camlost]

My recollection was that Nick (FAAngband author) was backporting his changes to Oangband.

[CJNyfalt]

Originally Posted by camlost

My recollection was that Nick (FAAngband author) was backporting his changes to Oangband.

I got that impression too, but is he willing to take over as maintainer?

[CJNyfalt]

I am watching a video about Git, and it looks that it might be the solution to the problem.

[Nick]

Here is the github repository that I was going to use to move O110u to AngbandBase. Feel free to fork it, or set up your own repository with either 110 or 110u, and do whatever you feel is appropriate.

As far as I'm concerned, I would be delighted if O had a proper maintainer - I have really just been keeping the seat warm. Now you just have to fight it out with Bahman

[Philip]

Originally Posted by Nick

As far as I'm concerned, I would be delighted if O had a proper maintainer - I have really just been keeping the seat warm. Now you just have to fight it out with Bahman

Hmm. Bahman doesn't want the seat, so I think it's free. Not that there are many non-UI changes that I can think of that would be good in O.

[CJNyfalt]

Originally Posted by Nick

Here is the github repository that I was going to use to move O110u to AngbandBase. Feel free to fork it, or set up your own repository with either 110 or 110u, and do whatever you feel is appropriate.

Well, I decided to create an Oangband github repo from 1.1.0. It can be found here:
https://github.com/CJNyfalt/Oangband
in case someone is interested. No changes yet.

[Magnate]

Originally Posted by CJNyfalt

Well, I decided to create an Oangband github repo from 1.1.0. It can be found here:
https://github.com/CJNyfalt/Oangband
in case someone is interested. No changes yet.

Thank you. I think this is awesome. With all of you, Nick and Bahman being not-maintainers, it's sure to develop brilliantly ;-)

[CJNyfalt]

I have now added those local changes that I felt was most useful and acceptable to the general public. So if someone is interested, take a look.
Here is the list:

Oangband 1.1.0 tweaked version
==============================

This is the list of changes from vanilla Oangband 1.1.0.

Gameplay changes
================
- Improved infravision to allow it to see walls and stuff but not take actions
that require light.
- Weak pseudo-id can now detect average items.

User interface
==============
- Highlight spell stat when choosing a character.
- Added x11-settings.prf support to main-x11.
- Show the effects of Clarity and Atheletics a bit better in character screen.
- Show the power of beguiling spells in spellbooks (slow, sleep,
confusion and fear), to encourage their use.
- Inscribe drops from uniques.
- Added monster list window.

Coding changes
==============
- Clean up X11 stuff on exit.
- Added missing depcomp.
- Removed files modified by autobuild system from repository.
- Fixed warning in acinclude.m4.
- Slight clean ups in birth.c.
- Sliggt clean ups in main-x11.c.

I still have some local changes I haven't added, but they messes with play balance, so I will probably have to branch for those.

I will probably take a look at AngbandBase stuff to merge in next.

[CJNyfalt]

Originally Posted by Nick

Here is the github repository that I was going to use to move O110u to AngbandBase. Feel free to fork it, or set up your own repository with either 110 or 110u, and do whatever you feel is appropriate.

As far as I'm concerned, I would be delighted if O had a proper maintainer - I have really just been keeping the seat warm. Now you just have to fight it out with Bahman

I am not interested in being maintainer, but I am interested to keep O updated and in sharing my changes to it. That is the good thing with git, everyone can have their own version and share code.

As for 110u, well, it is missing one of the killer feature in 110, so I stuck to 110.