Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

Keep the vanilla ones

Use an expanded vocabularly

Start entirely from scratch

Cull the words that don't make sense from vanilla, then add words as we go

Other(post it in the comments)

[chaotic skies]

*silent bump*

[TheError]

I'll sign up for a modding turn.

[pikachu17]

Is this dead? either way i'll take a turn

[chaotic skies]

I'm not sure. I hope it's not dead; if we start over that would be part 4, and none of the others have been finished. Not looking good for this thing so far. Oh well.

[TheError]

I'll begin my turn in a few days.

[TheError]

Actually I'll start later, someone else can start.

[chaotic skies]

Alright, I'm going to give this, say, a week. Then I'm going to take it over.

[vyznev]

Search for the df_announce_decode.pl and df_announce_encode.pl files from the very first thread. Download them. Then, for example, you could type:

Code: [Select]

perl df_announce_decode.pl df_linux/data/announcement/* > /tmp/announcement.txt
Into the console to have every file in the announcement folder decoded into the annoucement.txt in the tmp folder. Using them as a base, make a new file as you wish, like, rewriting messages or changing around when the elves come or whatever, then type:

Code: [Select]

perl df_announce_encode.pl /tmp/announcement.txt > df_linux/data/announcement
To encode it back. Please note that while you can decode multiple files at once, you can only encode one file at a time.

Guy who originally wrote those scripts here. Nice to see that people are still keeping this idea alive! 

I actually have an improved version of those scripts in my old github repo from the first thread.  I merged them into a single script, and added some fancy command line switches.  The idea is that you can run it once with the --reverse switch, like this:

Code: [Select]

perl text_to_data.pl --basedir=df_linux/ --reverse
and it'll (try to) decode all the encoded data files in df_linux/data into normal text files in a new directory named df_linux/data_src.  Then you can edit them as you like, and run it again:

Code: [Select]

perl text_to_data.pl --basedir=df_linux/
which will re-encode all the files that you edited.  (It looks at the file timestamps to see which files have been changed.)

The improved script can (or at least could) also decode and re-encode a bunch of files that the original scripts couldn't, including the data/index file that contains a bunch of paths to other files (among other things). Alas, there's some kind of a hardcoded checksum that I never managed to reverse engineer, so changing most of the strings in the index file will (would) cause DF to error out. Also, it should be noted that I haven't tried any of these scripts on recent DF versions, so for all I know some change might've broken them. Caveat emptor.

There's a bunch of other potentially useful scripts in that github repo too, like a rudimentary raw validator, a mineral color/symbol previewer (because the original project had a bunch of really weird looking stones due to people screwing up the color codes) and a little helper script for spell-checking DF raws with ispell.

BTW, regarding github in general, I still think it would be (close to) the ideal tool for a project like this, but only if all the people involved actually know how to use it (at least at a basic level, i.e. forking and cloning a repo, committing changes, pulling and pushing and making pull requests).  If most people can't or won't use it, then the few that do will end up having to keep track of everyone else's changes, and if they get busy with other things (as happened to me back then), the whole github thing will just fizzle out.

[chaotic skies]

I could probably manage github, as summer is coming up and I'm going to have a bunch of free time. It would still be better if people didn't have to wait for me to be on to do anything, but oh well

[Cerapter]

Oh hey there, vyznev. An updated script for encoding and decoding is good to hear.

And I'll be honest, I REALLY want to use git. Maybe not necessarily github, but git. Problem is, literally no one on the internet who uses it can teach it, and thus, I do not know myself how to use them.

[Dwarf4Explosives]

How to use git:
1: Download sourcetree.
2: Make a repository on github.
3: Link your copy of sourcetree to repository.
4: Add files to the folder associated with your repository.
5: Stage and commit files, then push to origin.

[DolosusDoleus]

((Psst. This thread is kinda dead. If y'all want to garner interest from more people, I'd reccomend starting a new thread. If you want to keep the progress from this thread, I'm sure the OP will be happy to let you do so.))

[Cerapter]

So I have made a Github page for the upcoming 4th editions, assuming we will have one. I have practised enough with Git in the meantime, and it does not seem menacing.

Still I'd like you guys to check if what I have written so far seems okay, regarding Git(hub) usage, that is. I actually downloaded GitKraken, and am using that right now, it's pretty neato.

If you guys deem it okay, we might go ahead and make a new thread for the fourth edition, where we finalise rules and agree on the submission standards and shit.

[chaotic skies]

I'd say that's okay. This one was pretty slow going to begin with, and this way if someone leaves for a while everyone else can keep working and not have to worry about it.

[Cerapter]

Yup, the stalling is why I want a full git-based one.

In fact, I'm making a thread for it.