Source Request: ROM w/colour

Posted by Irinami on Sat 08 Sep 2001 11:12 PM — 13 posts, 41,452 views.

#0
After a few days of trying to get ROM /WITH/ colour(including GhostMUD, which almost worked save a glitch wherein it wouldn't recognize level 60+ char's as Imm's) to compile under CygWin, I'm asking for help.

Does any kind soul have sources for ROM with colour a la Lope's? I don't care if it has OLC or not (that's a mere detail), I just want my users to be able to insert their own colours. Plenty of MUD's have colour for building and help files, but I'm at a loss to find or create true full-colour for everyone.

It's either ask for the source, or ask for someone who knows how to apply Lope's patch by hand.

Either way, thanks in advance.
--Iri
Amended on Sun 09 Sep 2001 01:15 AM by Irinami
Australia Forum Administrator #1
I got this to work like this:

Unzip Rom24b2 file:


tar xzvf Rom24b2.tar.gz
cd Rom24/src


Apply the patch:


$ patch < patch_rom24_colour2.0
patching file `act_comm.c'
Hunk #1 succeeded at 99 (offset -1 lines).
Hunk #3 succeeded at 270 (offset -7 lines).
Hunk #5 succeeded at 308 (offset -7 lines).
Hunk #7 succeeded at 364 (offset -7 lines).
Hunk #9 succeeded at 419 (offset -7 lines).
Hunk #11 succeeded at 461 (offset -7 lines).
Hunk #13 succeeded at 516 (offset -7 lines).
Hunk #15 succeeded at 571 (offset -7 lines).
Hunk #17 succeeded at 626 (offset -7 lines).
Hunk #19 succeeded at 681 (offset -7 lines).
Hunk #21 succeeded at 701 (offset -7 lines).
Hunk #23 succeeded at 744 (offset -7 lines).
Hunk #25 succeeded at 876 (offset -7 lines).
Hunk #27 succeeded at 948 (offset -7 lines).
Hunk #28 succeeded at 1958 (offset 12 lines).
patching file `act_info.c'
patching file `act_wiz.c'
Hunk #1 succeeded at 187 (offset 3 lines).
patching file `comm.c'
Hunk #1 succeeded at 1313 (offset -8 lines).
Hunk #3 succeeded at 1333 (offset -8 lines).
Hunk #5 succeeded at 2310 (offset -3 lines).
Hunk #7 succeeded at 2392 (offset -3 lines).
Hunk #9 succeeded at 2650 (offset -3 lines).
patching file `fight.c'
patching file `handler.c'
Hunk #1 succeeded at 2941 (offset 32 lines).
patching file `interp.c'
patching file `interp.h'
Hunk #1 succeeded at 96 (offset 1 line).
patching file `merc.h'
Hunk #2 succeeded at 158 (offset -1 lines).
Hunk #7 succeeded at 2459 (offset -1 lines).
patching file `recycle.c'
patching file `save.c'
Hunk #4 succeeded at 1094 (offset -14 lines).
Hunk #6 succeeded at 1401 (offset -14 lines).
patching file `tables.c'


Change file Makefile:


NOCRYPT = -DNOCRYPT -DOLD_RAND


Compile:


make


Run:


cd ../area
../src/rom.exe


If these steps don't work for you please advise exactly which files you are using. eg. version of ROM, which colour patch you are using, where you got it, and so on.

Also please state in what way it did't work...

1. Didn't patch
2. Didn't compile
3. Didn't run


Amended on Sat 24 Nov 2001 09:39 PM by Nick Gammon
#2
To get my mind off things, I attacked this problem from a new vector: Versions.

I had been applying Lope's patch to ROM2.4b6, since the dates in Lope's files were later than the release date in the ROM2.4b6's README.version file. I even finally got it applied by hand, which was easy when I stared at the patch file format for a long time.

The problem was, after compiling, I had StuttusutututterMUD. That is, when you turned colour on (via the 'colour' command), the MUD would show something like...

ccocolcolocoloucolourcolour colour ocolour oncolour on colour on

Now, looking closely at that, it appears to me that as each character is being checked for colour, it is being sent to the character as well (instead of just kept internal in memory or whatnot).

Just this morning, I d/l'ed ROM2.4b4 and applied the patch (Lope's coloUr v2.0)... no problems! Everything went A-OK, and I no longer had StututttutterMUD.

So now this thread is more of a notice--if you find problems applying Lope's coloUr to vanilla ROM, try applying it to a previous version.

Thanks for being so active of a head of this little community, Nick. ^_^

--Iri
Australia Forum Administrator #3
I initially tried with 2.4b6 and got some patch errors, so I went back a couple of versions, which is what I got to work.
#4
Okay I have just loaded all of the files etc. My friend emailed me some of his areas and everything and I am not that great with ROM. I got it to get the areas from F:/1/area (my folder for ROM areas) and after two lines the ROM turns off and exits. How do I fix this problem and what is happening. I dont have enough time to read what is being typed by ROM because it exits before I have time to read it. Any help is great thanks.
-Kevin
Australia Forum Administrator #5
I would open a command window, rather than just double-clicking on rom.exe. Then the window will stay open and you can see what the error message is.
#6
OK this is what it is saying;

F:\1>rom.exe
Working directory now F:\1\area
Tue Feb 12 14:36:35 2002 :: [*****] FILE: immort/are LINE: 1
Tue Feb 12 14:36:35 2002 :: [*****] BUG: Boot_db: bad section name.

If you can help me out, thanks
-Kevin

Australia Forum Administrator #7
Sounds like a problem with immort/are (or it it immort.are?).

Try posting the first dozen lines from that file.
#8
#AREADATA
Name Valhalla~
Builders None~
VNUMs 1200 1299
Credits {W[ {OIMM {W] {wRom {CI{cmmortal {CZ{cone {x~
Security 9
End



#MOBILES
#1200
Heimdall~
Heimdall~
Heimdall, guardian of Bifrost, stands guard over the Rainbow Bridge.
~

I also tried to remove the immort.area file, but then i got an error of file not found.
Australia Forum Administrator #9
Looks like a newer format area file. Here is an example from midgaard.are, you can see the first few lines are different, in particular you need AREA rather than AREADATA ...


#AREA
midgaard.are~
Midgaard~
{ All } Diku Midgaard~
3000 3378

#MOBILES
#3000
wizard~
the wizard~
A wizard walks around behind the counter, talking to himself.
~
#10
I just removed immort.are, and i got the same error, Boot_db again so I need to find out how to solve that.
Australia Forum Administrator #11
Quote:

My friend emailed me some of his areas and everything

...

I just removed immort.are, and i got the same error, Boot_db again so I need to find out how to solve that.



It sounds like all your friend's areas are like that. You will need to fix all of them. Presumably this error now occurs in a different area as you are no longer using immort.are.

#12
A few notes RE: GhostMUD....

1) In the instructions it says there is a yahoogroup had this question been posted there i would have answered MUCH sooner.

2) GhostMUD out of the box has 110 levels not 60 so a level 60 character is not an immortal.

There you go :-)

Besides that the color/olc and other changes work fine and on the yahoo group are the only 2 known issues or bugs.

Taka
a_ghost_dancer@excite.com
telnet bb12.betterbox.net:3333