Why aren't you playing Unangband?

[andrewdoull]

This is another good options. That will teach them, newbies! But seriously, this is better than current messages. Give them a warning and if they disregard it, let them appear on the next wilderness location paralized from starvation. This is much more colorful experience than hitting '<' and seeing no reaction. It's even sensible from a role-playing perspective. BTW, the current travel food consumption is so toned-down that most newbies will not even notice before Rivendell, I guess.

Okay. Lets go this way. The 'need to be full' pre-requisite is probably a bit harsh anyway for starving adventurers fleeing the dungeon anyways...

[Bandobras]

Yeah, don't give 'em a message and let 'em starve.

This is another good options. That will teach them, newbies! But seriously, this is better than current messages. Give them a warning and if they disregard it, let them appear on the next wilderness location paralized from starvation. This is much more colorful experience than hitting '<' and seeing no reaction. It's even sensible from a role-playing perspective. BTW, the current travel food consumption is so toned-down that most newbies will not even notice before Rivendell, I guess.

[Geofferic]

You mean like 'You need a full stomach for the road ahead.'

Or is that too subtle?

Well you might be more explicit in the first town.

I'm not really sure I understand why it's forced, tho. You could just prompt them if they're sure they want to leave without a full stomach.

[Nick]

You mean like 'You need a full stomach for the road ahead.'

Or is that too subtle?

Yeah, don't give 'em a message and let 'em starve.

[andrewdoull]

Why not just give an error message when you try to leave town without a full stomach?

"You can't leave yet, n00b, eat something!"

You mean like 'You need a full stomach for the road ahead.'

Or is that too subtle?

[Geofferic]

Why not just give an error message when you try to leave town without a full stomach?

"You can't leave yet, n00b, eat something!"

[andrewdoull]

Wow, brilliant! Done in SVN (but I left some room in the starting stomach for quaffing potions, etc.).

The whole point of not starting with a full stomach is that you learn straight away that you have to be full in order to travel.

I'm going to roll this back... sorry guys.

Andrew

[Bandobras]

Wow, brilliant! Done in SVN (but I left some room in the starting stomach for quaffing potions, etc.).

[Geofferic]

Oh. Correct me if I'm crazy, but couldn't you just *start* with a full stomach upon character creation?

[Daven_26d1]

You have to have a full stomach before you can travel anywhere by pressing "<".

[Geofferic]

My biggest problem is that I can't seem to leave the first town. I *think* that it told me to hit < or > the first time I started the game, but neither works. So the game is kinda slow stuck in the first area...

[andrewdoull]

Sorry, the newest sources from Berlios compile for me without problems (make -f Makefile.std). Debian unstable.

Do you have the old sources around? Could you unpack them somewhere and do 'diff -r old_sources/ new_sources/'? I bet it's some corruption, either from download or ./configure...

Anyway, I still don't know what are the error messages you get on new freshly unpacked sources, with 'make -f Makefile.std'.

Its worth pointing out that there's two ways of getting the source:

1. Downloading from SVN.
2. A separate source distribution, that I compile using build_src.bat (or currently by copying and pasting the contents of build_src-osx into a term window, because I can't remember how to build a valid Unix shell file).

The separate source distribution doesn't have the /todo directory included which is why Nick's experiencing the problems with the todo directory. I can include it easily enough, along with the remaining steps.

However, I'd like to figure out at some point what's broken with the other parts of the Unangband linux build...

Andrew

[Bandobras]

Sorry, the newest sources from Berlios compile for me without problems (make -f Makefile.std). Debian unstable.

Do you have the old sources around? Could you unpack them somewhere and do 'diff -r old_sources/ new_sources/'? I bet it's some corruption, either from download or ./configure...

Anyway, I still don't know what are the error messages you get on new freshly unpacked sources, with 'make -f Makefile.std'.

Edit: I meant the packaged sources. Of course SVN compiles, too.

[Kav]

The thing is make -f Makefile.std worked on the sources that Andrew uploaded right before these. That is why I was asking what changed.

[Daven_26d1]

The errors now look like problems with X; I usually remove the references to x11 from the makefile, but this is harder when using ./configure. You might just be missing a path to your x11 libs.

On Kubuntu, which is Debian based, I made Makefile.std read:

NORMAL_CFLAGS = -Wall -pipe -O2 -D"USE_GCU" -D"USE_NCURSES"
LIBS = -lncurses

basically stripping out x11 support. I prefer *bands compiled with just basic ncurses anyway because you can play around with the fonts to make it look different. Be aware that this was using the "make -f Makefile.std" method inside src/ and then just "mv unangband ../unangband"

Couldn't hurt to try updating terminal definitions, package name is something like "ncurses-def" but if ncurses is compiling other *bands I don't think its that.