News | Forum | People | FAQ | Links | Search | Register | Log in
Quoth 2.2
Download | Map Packs | Changelog | Tutorial

Quoth version 2.2 is out! This is a spit-and-polish release, with some new features to play with, but the emphasis on refining the Quoth 2 content, re-balancing some monsters, fixing old bugs, and keeping Quoth as lightweight as possible.

The download links can be found above. There are two version: a full install of Quoth, and a patch that will upgrade 2.0 and 2.1 to 2.2. If you have 2.1, you will need to replace the existing pak2.pak file with the new one supplied.

Thanks to everyone who has tested and helped out to get this release together!
First | Previous | Next | Last
Ok, you replaced it. That makes a great deal of sense then, very likely is network backbone-level caching. Which can be a real pain. 
I just downloaded the file and it's May 2014 still.

Probably should have a couple of other people other than myself check it out because I'd feel real bad if somehow it is just me.

Like negke since he reported the problem. 
(I did not click a wrong link, I assure you and I downloaded it twice). 
I just downloaded the link in post #65

Inside is a text file called quoth2_2.txt

Inside that is a legal notice including the date "May 2014" 
oh, but it does have a pak2.pak with a date of 11/11/2016 
Ok, just me. Ignore me. Important thing is problem solved.

Maybe caching works with a database that ignores punctuation and hashes the alphanumerics. 
Not Just You Baker 
Just downloaded it for the 1st time with the link in #65 and got pak2.pak, 8.0 MB from May 3rd 2014 @05:24

So this REALLY is the most recent file though? 
Have you extracted the file and checked if it displays the same modified date? Perhaps there's some glitch with the zip if you overwrite the file within a zip which puts the archive goes out of sync with the actual file - and that might cause the displayed date to be OS dependent.

Then again, maybe the OS dependency will also appear on the extracted file. Here are some file hashes to check for pak2.pak:
MD5: 69c2c4880ccb367cee1e338194d47184
SHA-1: e357e0b2b78703e2ebb32ab822911b77c4b0a37a 
Wrong Tense 
Perhaps there's some glitch with the zip if you overwrite the file within a zip which puts the archive goes out of sync with the actual file

To clarify, because it looks like I've written this sentence in the second person. When I made the zip file, I didn't rebuild the zip from scratch. Instead, I too the original zip and overwrote the pak2.pak file from 2.2.1 with the 2.2.2 pak file, using Windows Explorer. I'm speculated that this could cause a glitch, especially one that isn't apparent from a Windows POV. 
Today I learned that there's still someone out there who uses Windows Explorer to handle .zip files.

Considering that "proper" archive tools can sometimes struggle and choke up when making changes, I always choose to completely recreate my archives when I update them. Even if that means just extracting the old one, adding in the new files/replacing the out of date ones, and recompressing it, it's just a little peace of mind that I like to have when releasing content...

I feel like a lot of the issues in recent posts could have been helped by keeping different versions of Quoth more distinct from each other in this manner. Another help might have been to keep unique file names, if it is some sort of web caching interfering with downloads. 
Alright ... Sensible "extend A Mod" And Quoth Versioning 
Preach, since you are only guy in universe with any experience maintaining such a mod.

I've been thinking this over off and on, and here's what I've got for raw ideas after considering bad factors.

/Not that I am optimistic that anyone besides yourself (and on a good day) is going to be capable in maintaining a multi-game dir mod, but that's beside the point. But Sock also seems like a particular picky fellow that is set in his ways, which is a major strength for this ... so anyways ...

Quoth - Indicate version

-quoth:1 <--- load through pak1.pak
-quoth:2 <--- load through pak2.pak
-quoth:3 <--- load through pak3.pak

If I recall, original Quoth had 2 pak files. And then Quoth 2 had 3 of them. Then Quoth 2.1 had 4 of them.

Under this system, it would have been preferable for the names to be Quoth 1, Quoth 2, Quoth 3, etc.

But the point is this would allow a single Quoth mod but allow version specific loading.

Why a colon? Because it is an illegal character for Windows filenames, no one can have a gamedir named "quoth:1"

Sensible Double-gamedir


-game mapjam85 -arcane // Quake mod using "arcane"
-game mapjam85 -arcane -hipnotic // Quake mod using "arcane" requiring hipnotic extensions
-game mapjam85 -arcane:2 // Load thru pak2

The -arcane:2, like the Quoth examples, could allow your onion layer versioning and allow a prior version of "arcane" to be used.

(* Since -quoth is known to require -hipnotic, would be the sole exception to the rule.)

This would allow people to keep doing what they are already familiar with doing and everything works the same.

Anyway, these thoughts provided for your feedback. 
I got your meaning. Thank you for the hashes, I'll check them against what I have. 
Pak Strategy 
The idea with the pak files was to allow simple upgrades from one patch to another without needing to download lots of stuff again (remember, this plan was invented in 2005 when people had to worry a bit more about bandwidth). So the idea was that you could upgrade to 2.2 straight from 2.1 or 2.0, and 3.0 would work in the same way, replacing pak2.pak, making an upgrade which works from version down to 2.0. Then 3.1 up to 4.0 would be pak3.pak, etc...

I have to ask, given how hard we work on backwards compatibility in the mod, why you think there's a pressing need for playing earlier versions? Is there a specific issue with a map we need to shim in the next patch? 
Probably Wrong But.. 
I think it's not so much about quoth specifically, so much as allowing mods to use a similar system, but in the event that they don't have that level of backwards compatibility, to allow easy loading of older versions. 
Various Reasons 
a) For original experience at map release time as an option.
b) Testing and checking for a material behavior difference.
c) Fallback if something if bug or issue with current version, without the user having to reinstall an older Quoth to work around it.

I know some of the mild changes like changing the voreling health don't mean much to most people.

But for instance, if I want to reply an old map that I liked, I'd like to easily replay it with exactly the same rules and behavior in effect that were there the first time. At least as an option.

What if I want the voreling to be annoying and require 2 super-shotgun blasts to kill because when I played the map originally it had annoying vorelings?

One irony is that certain releases are actually mostly exempt from Quoth upgrades because they have their own progs (Metal Monstrosity, for instance). 
Also what Pritchard said.

You pioneer the incremental mod release idea with the additive pack concept.

If others follow your lead, my above scheme is a way that full compatibility is always an option. 
@preach - Issue Example 
1) I take from Quaddicted.
2) I take Quoth 2.2.2 zip which I am assuming is current version 8,035,386 bytes (pak2.pak size, working on assumption that the date of May 3 2014 is error of the zipping tool).
3) Using the glwarp.exe provided with the Warpspasm download I do this ...

c:/quake/glwarp.exe -game warp -quoth

What I get when I startup
*) I get Quoth demos playing.

What I am supposed to get when I startup
*) I should get the Warpspasm start demos playing.

Basically, playing Warpspasm with current Quoth I can't get the intended Warpspasm experience.

(I wouldn't have to use glwarp.exe, I could instead use Mark V or BengtQuake or the Requiem engine --- all which support the Warpspasm demos that are in protocol 10002.)

So anyway, an example. 
Backwards Compatibility 
I have responded in much more complexity than was perhaps necessary here 
I think that is a cool thread.

Anyway, I think a "Touch of Evil" is going to be my in-engine short-term solution for the Warpspasm issue to make it so the presentation is right ...

if (game == warpspasm && command == startdemos)
... if (startdemos != "demo1 demo2 demo3") then make it so

You are happy. I am happy. Someone wanting the Warpspasm experience is happy.

Somewhere an Evil God of Proper Coding is looking down at me with a frown --- but that happens all the time.

/Quoth 2.2 at Quaddicted on last check is still 2.2.1, btw. I checked rather recently and the byte size of pak2.pak is not same as your Quoth 2.2.2. 
So when's Quoth 2.3 coming out? 
Skybox Format 
Is this the same format and orientation for the skyboxes in the Quoth pak files? Or are some of the locations different? I thought I'd ask as I don't have a ton of time for trial and error. The one time I've tried it was a disaster.

I would like to do my own from Space3d 
This is really more of an engine thing than a Quoth specific question, but I think I have figured it out. If you change the filename suffixes in the following way everything should align:

pos_y -> up
pos_z -> bk
pos_x -> rt
neg_z -> ft
neg_x -> lt
neg_y -> dn 
lt+rt are flipped in relation to normal cubemaps, iirc.
this means that the other 4 images are flipped on various axis too or whatever, which means simple renaming isn't exact.

If you don't really care that your cubemap is basically inside out then whatever just go ahead and rename them, but if you want to map them exactly then you need to do more than just rename them. Probably for embedded space scenes you won't care. 
@spike & @Preach 
Thank you guys so much. I was just sitting down to do a simple number 1-6 cubemap in PS to see what could be flipped etc. This helps a lot. 
Confirming Skybox 
pos_y -> up
pos_z -> bk
pos_x -> rt
neg_z -> ft
neg_x -> lt
neg_y -> dn

Tested in Quakespasm - this is the right configuration! Thanks again. 
First | Previous | Next | Last
You must be logged in to post in this thread.
Website copyright © 2002-2024 John Fitzgibbons. All posts are copyright their respective authors.