Shadow over the Pathoras 1.1 Released

[WolfSoft]

Shadow over the Pathoras is an epic adventure mod for GZDOOM that takes place in year 1650.

The story takes place in year 1650, when Ferdinand III. sends royal naval officer William Wolf and his assistant to England due to important business. They get caught by a storm on the way, so they decide to anchor next to a nearby island. What they don't know is, that the island is a part of an empire named Pathoras, where 20 years before a tragedy took place when miners found an entrance to hell. Shortly after a 10 years long war happened against "invaders from beneath". Citizens of Pathoras lost the war and a bunch of traitors started to rule the Pathoras. William finds an entrance to an old mine on the shore of the island, but when he enters it, the entrance caves in. Now he must find out, what happened to the country and help the people who still want to fight...

Features :
58 levels spread across 11 hubs.
A large variety of environments - woods, swamps, mines, deserts...
Single player campaign, Coop arena and 12 levels from single player for Deathmatch for up to 8 players.
12 weapons - from bare hands, sabre, mace to blunderbuss, axe and sword.
2 tools - torch and shield.
Weapon enchanting.
17 kinds of enemies.
A lot of original puzzles
instructions are packed in the zip

When I started developing this mod I borrowed a few things from GZDoom 2.2.0 decorates and also used this version during the development. From what I noticed, the newer versions of GZDoom break certain items and weapons - it tries to rename them, because the have the same names as some items from Heretic/Hexen, but this breaks then and so they don´t work as they should.

Special thanks to : Doomer97, Foulerworm, Jr1616 and Leebigh.

So unfortunately this mod is for GZDOOM 2.2.0 only !

Download : http://www.moddb.com/mods/shadow-over-the-pathoras or http://www.mediafire.com/file/hopx774ul ... _1.0.1.rar

Screenshots :

---

Trailer :


This post was reconstructed from a browser cache. Please do not blank posts at the slightest hint of negative feedback. Thanks. -mgmt

[Blue Shadow]

So you're denying people from using newer versions of the engine because you didn't put a good effort in naming your actor classes. Shame, really, considering how interesting the project sounds.

[_mental_]

Download Error
The file requested (SOTP_1.0.2.rar) is for members only. Join now to start downloading.

Is this intentional restriction?

[WolfSoft]

So you're denying people from using newer versions of the engine because you didn't put a good effort in naming your actor classes. Shame, really, considering how interesting the project sounds.

You are the first one who complains about it - people on MODB and DoomWIP are okay with it. This was build and tested with 2.2.0 without any issues, so it´s not my fault that new GZDoom can´t handle decorate replacing.

Didn't put a good effort in naming actor classes - okay, so if the older version has no problem with it you expect the new one to be the same, right ?

[WolfSoft]

Is this intentional restriction?

Kinda, but I updated the first post with an alternative link.

[wildweasel]

You are the first one who complains about it - people on MODB and DoomWIP are okay with it. This was build and tested with 2.2.0 without any issues, so it´s not my fault that new GZDoom can´t handle decorate replacing.

The console warns you about it and everything, though - "Tried to register class more than once" should be a pretty clear indicator that you're not supposed to do that, right? =P

[WolfSoft]

This is getting kinda off topic, so these are my last words to this GZDoom "issue" - I know, but the difference is that the old version overwrites the default decorate and the new does not.

[Enjay]

The console warns you about it and everything, though - "Tried to register class more than once" should be a pretty clear indicator that you're not supposed to do that, right? =P

In fact, there are console warnings throughout the mod about DECORATE and mapping errors.

@WolfSoft: It's not so much that newer GZDooms cannot handle what you have done in your mod. It's that the problems being reported by GZDoom have always been errors, even back in the version of GZDoom that you are using. The main change in GZDoom is that it has got better at reporting errors that, previously were not reported.

For what it's worth, here are the errors reported by GZDooms Git build from today. I guarantee that many of the mapping errors at least (and probably some of the others) would have also been reported by version 2.2.0.

---

Code: Select all • Expand view

Script warning, "SOTP10.pk3:decorate" line 137:
Tried to define class 'MEAT' more than once. Renaming class to 'MEAT@SOTP10.pk3@decorate'
Script warning, "SOTP10.pk3:decorate" line 1444:
Tried to define class 'SilverKey' more than once. Renaming class to 'SilverKey@SOTP10.pk3@decorate'
Script warning, "SOTP10.pk3:decorate" line 2362:
Tried to define class 'Coin' more than once. Renaming class to 'Coin@SOTP10.pk3@decorate'
Script warning, "SOTP10.pk3:decorate" line 3021:
Tried to define class 'Rock2' more than once. Renaming class to 'Rock2@SOTP10.pk3@decorate'
Script warning, "SOTP10.pk3:decorate" line 3033:
Tried to define class 'Rock3' more than once. Renaming class to 'Rock3@SOTP10.pk3@decorate'
Script warning, "SOTP10.pk3:decorate" line 3070:
Tried to define class 'ZCorpseKabob' more than once. Renaming class to 'ZCorpseKabob@SOTP10.pk3@decorate'
Script warning, "SOTP10.pk3:decorate" line 3799:
Tried to define class 'Meat2' more than once. Renaming class to 'Meat2@SOTP10.pk3@decorate'
Script warning, "SOTP10.pk3:decorate" line 4502:
Tried to define class 'Dart' more than once. Renaming class to 'Dart@SOTP10.pk3@decorate'
Script warning, "SOTP10.pk3:decorate" line 4603:
Tried to define class 'Blaster' more than once. Renaming class to 'Blaster@SOTP10.pk3@decorate'
Script warning, "SOTP10.pk3:decorate" line 4674:
Tried to define class 'Chase_Water' more than once. Renaming class to 'Chase_Water@SOTP10.pk3@decorate'
Script warning, "SOTP10.pk3:decorate" line 4801:
Tried to define class 'Moss1' more than once. Renaming class to 'Moss1@SOTP10.pk3@decorate'
Script warning, "SOTP10.pk3:decorate" line 4815:
Tried to define class 'Moss2' more than once. Renaming class to 'Moss2@SOTP10.pk3@decorate'
Script warning, "SOTP10.pk3:decorate" line 7121:
Tried to define class 'PILCAV' more than once. Renaming class to 'PILCAV@SOTP10.pk3@decorate'
Script warning, "SOTP10.pk3:decorate" line 1:
Tried to define class 'Clip' more than once. Renaming class to 'Clip@SOTP10.pk3@decorate'
Script warning, "SOTP10.pk3:decorate" line 255:
Tried to define class 'Crossbow' more than once. Renaming class to 'Crossbow@SOTP10.pk3@decorate'
Script warning, "SOTP10.pk3:decorate" line 458:
Tried to define class 'Arrowdropped' more than once. Renaming class to 'Arrowdropped@SOTP10.pk3@decorate'
Script warning, "SOTP10.pk3:decorate" line 493:
Tried to define class 'Mace' more than once. Renaming class to 'Mace@SOTP10.pk3@decorate'
Script warning, "SOTP10.pk3:decorate" line 1049:
Tried to define class 'AxePuff' more than once. Renaming class to 'AxePuff@SOTP10.pk3@decorate'
script parsing took 136.77 ms
Script error, "SOTP10.pk3:gldefs" line 508:
Warning: dynamic lights attached to non-existent actor UndeadHunter

Editor number 10504 defined twice for classes 'TreeLarge2' and 'NfreeDead1'
Editor number 7597 defined twice for classes 'PILCAV@SOTP10.pk3@decorate' and 'PILCAV'

R_InstallSpriteLump: Bad frame characters in lump ARTISKL2
R_InstallSpriteLump: Bad frame characters in lump ARTIPWBK
R_InstallSpriteLump: Bad frame characters in lump ARTIBOK2
R_InstallSpriteLump: Bad frame characters in lump ARTIBMAN
R_InstallSpriteLump: Bad frame characters in lump SWAJX0PN
R_InstallSpriteLump: Bad frame characters in lump HWARI0PN

<------------------------------->

map02 - The Beach

Unknown bottom texture 'RAYFL32' on first side of linedef 610
Unknown bottom texture 'RAYFL32' on first side of linedef 646
Unknown bottom texture 'RAYFL32' on first side of linedef 650
Unknown bottom texture 'RAYFL32' on first side of linedef 654
]map map03

<------------------------------->

map04 - The Beach

Unknown bottom texture 'RAYFL32' on first side of linedef 563
Unknown bottom texture 'RAYFL32' on first side of linedef 599
Unknown bottom texture 'RAYFL32' on first side of linedef 603
Unknown bottom texture 'RAYFL32' on first side of linedef 607
]map map05

<------------------------------->

map05 - The Mine

Line 419 has no first side.
Line 3077 has no first side.
Line 3078 has no first side.
Line 3079 has no first side.

<------------------------------->

map09 - Blandadeur

Line 1846 has no first side.
]map map10

<------------------------------->

map11 - Flumentumer

Unknown middle texture 'WD_B_2_1' on first side of linedef 109
Unknown middle texture 'WD_B_2_1' on first side of linedef 129
Unknown middle texture 'WD_B_2_1' on first side of linedef 119
Unknown middle texture 'WD_B_2_1' on first side of linedef 145
]map map12

<------------------------------->

map12 - Flumentumer

Unknown middle texture 'WD_B_2_1' on first side of linedef 178
Unknown middle texture 'WD_B_2_1' on first side of linedef 188
]map map13

<------------------------------->

map16 - Cracrer

Line 6051 has no first side.
]map map17

<------------------------------->

map22 - New City

Script error, "maps/map22.wad" line 155:
Expected '=' but got identifier 'conversation' instead.

<------------------------------->

map29 - Baneforg

Unknown top texture 'WD_B_2_1' on second side of linedef 5
Unknown top texture 'WD_B_2_1' on first side of linedef 7
Unknown bottom texture 'WD_B_2_1' on second side of linedef 5
Unknown bottom texture 'WD_B_2_1' on first side of linedef 7
Unknown top texture 'WD_B_2_1' on second side of linedef 10
Unknown top texture 'WD_B_2_1' on first side of linedef 11
Unknown bottom texture 'WD_B_2_1' on second side of linedef 10
Unknown bottom texture 'WD_B_2_1' on first side of linedef 11
Unknown top texture 'WD_B_2_1' on second side of linedef 11
Unknown top texture 'WD_B_2_1' on first side of linedef 12
Unknown bottom texture 'WD_B_2_1' on second side of linedef 11
Unknown bottom texture 'WD_B_2_1' on first side of linedef 12
Unknown top texture 'WD_B_2_1' on second side of linedef 12
Unknown top texture 'WD_B_2_1' on first side of linedef 14
Unknown bottom texture 'WD_B_2_1' on second side of linedef 12
Unknown bottom texture 'WD_B_2_1' on first side of linedef 14
Unknown top texture 'WD_B_2_1' on second side of linedef 38
Unknown top texture 'WD_B_2_1' on first side of linedef 45
Unknown top texture 'WD_B_2_1' on second side of linedef 46
Unknown top texture 'WD_B_2_1' on first side of linedef 56
Unknown top texture 'WD_B_2_1' on second side of linedef 47
Unknown top texture 'WD_B_2_1' on first side of linedef 57
Unknown top texture 'WD_B_2_1' on second side of linedef 68
Unknown top texture 'WD_B_2_1' on first side of linedef 80
Unknown bottom texture 'WD_B_2_1' on second side of linedef 68
Unknown bottom texture 'WD_B_2_1' on first side of linedef 80
Unknown top texture 'WD_B_2_1' on second side of linedef 86
Unknown top texture 'WD_B_2_1' on first side of linedef 99
Unknown top texture 'WD_B_2_1' on second side of linedef 94
Unknown top texture 'WD_B_2_1' on second side of linedef 109
Unknown top texture 'WD_B_2_1' on second side of linedef 95
Unknown top texture 'WD_B_2_1' on first side of linedef 111
Unknown top texture 'WD_B_2_1' on second side of linedef 116
Unknown top texture 'WD_B_2_1' on first side of linedef 134
Unknown bottom texture 'WD_B_2_1' on second side of linedef 116
Unknown bottom texture 'WD_B_2_1' on first side of linedef 134
Unknown top texture 'WD_B_2_1' on second side of linedef 134
Unknown top texture 'WD_B_2_1' on first side of linedef 152
Unknown top texture 'WD_B_2_1' on second side of linedef 142
Unknown top texture 'WD_B_2_1' on first side of linedef 162
Missing texture 'WD_B_2_1' is used 21 more times

<------------------------------->

map31 - Dungeons of Terian

Unknown middle texture 'W_020' on second side of linedef 2422

<------------------------------->

map37 - Wraanet

Line 1633 has no first side.

<------------------------------->

map39 - Tereagen

Line 6456 has no first side.
Line 6457 has no first side.
Line 6458 has no first side.
Line 6459 has no first side.
]map map40

<------------------------------->

map41 - The Ossuary

Script error, "maps/map41.wad" line 1:
Map does not define a namespace.

]map map42

<------------------------------->

map43 - The Mine

Line 756 has no first side.
Line 784 has no first side.
Line 811 has no first side.
Line 827 has no first side.
]map map44

<------------------------------->

map48 - The Royal Castle

Line 396 has no first side.
]map map49

<------------------------------->

map53 - Credits

Unknown bottom texture 'RAYFL32' on first side of linedef 92
Unknown bottom texture 'RAYFL32' on first side of linedef 133
Unknown bottom texture 'RAYFL32' on first side of linedef 107
Unknown bottom texture 'RAYFL32' on first side of linedef 159
Unknown bottom texture 'RAYFL32' on first side of linedef 117
Unknown bottom texture 'RAYFL32' on first side of linedef 179
Unknown bottom texture 'RAYFL32' on first side of linedef 134
Unknown bottom texture 'RAYFL32' on second side of linedef 200
]map map54

<------------------------------->

map54 - Victory

Line 1635 has no first side.
Line 1671 has no first side.
Line 5408 has no first side.
Line 5427 has no first side.


[WolfSoft]

Okay,

There is no rule that prevents me from using an older version of ANY port whatsoever. You are acting like this gonna cause a nuclear war or something like that.

Okay, next time you start a thread about some project you are making I will post ALL bugs and errors you have in it, just because thats what everybody does, right ?

Done.

[wildweasel]

There is no rule that prevents me from using an older version of ANY port whatsoever. You are acting like this gonna cause a nuclear war or something like that.

Not at all - it'd just be nice if a person didn't have to dig for a specific version of GZDoom to play your mod. Because beyond the updates to the scripting engine that are the source of your headaches, there has been a large amount of bug fixes to the rest of the engine that, in some users' cases, mean the difference between the game running at all, or just crashing to desktop for no reason.

Okay, next time you start a thread about some project you are making I will post ALL bugs and errors you have in it, just because thats what everybody does, right ?

Done.

That is in fact a good thing to do and can help projects be cleaner, more compatible, and less likely to break when GZDoom needs to make major changes to the back-end.

[Enjay]

There is no rule that prevents me from using an older version of ANY port whatsoever. You are acting like this gonna cause a nuclear war or something like that.

No need to get all upset. I posted the errors because they are errors. More importantly, I posted them because I thought the mod was good, and therefore worth fixing.

Okay, next time you start a thread about some project you are making I will post ALL bugs and errors you have in it, just because thats what everybody does, right ?

Ummm, yes, that is what many people do, and please do it for my mods. If you find an error in one of my mods, it's almost certainly because I missed it myself and I will probably want to fix it.

[WolfSoft]

Like GZdoom 2.3.0 and 2.3.1 ? These are the best 100% bug free, totally tested builds in the history of GzDoom...or not ?

[wildweasel]

Like GZdoom 2.3.0 and 2.3.1 ? These are the best 100% bug free, totally tested builds in the history of GzDoom...or not ?

Probably best to target the version available on the front page of ZDoom.org, since that's what most people see first.

[Rachael]

When GZDoom 2.4.0/3.0.0 fail to start your mod it's not because it is trying to be evil and buggy and what not. It is trying to get you to fix errors that are easily fixable. In this case, DECORATE replacement is only supported by naming the actor something else and using the "replaces" keyword to show what it is meant to replace - i.e.:

Code: Select all • Expand view

actor NewChicken replaces Chicken
{
  // fancy stuff here etc
}

There really was never a need for this hostility or overreaction towards it. A simple gander over at the wiki, or even just posting a few questions in editing (that's what it's there for, after all) would have saved everyone, especially the OP, a lot of trouble and heartache. The only "stupid" question is the one you refused to ask.

[WolfSoft]

Like GZdoom 2.3.0 and 2.3.1 ? These are the best 100% bug free, totally tested builds in the history of GzDoom...or not ?

Probably best to target the version available on the front page of ZDoom.org, since that's what most people see first.

Like the people that saw these builds back in January ?