[Released] The One

[Turboman.]

The One is a small/medium-sized mappack for the Oldunreal 227j patch, inspired by classic unreal community maps such as "Nali Cove", "One Day" or "Tashara’s Cove". But it utilizes oldunreal's 227j patch features such as improved stability and better graphical fidelity.

Download link for the 1.0 release is available here:
https://www.moddb.com/mods/unreal-the-o ... he-one-v10

Moddb page with additional info, screenshots and videos:
https://www.moddb.com/mods/unreal-the-one

Synopsis
Welcome to the island of K’tharia. The Nali have established a peaceful haven here, free from oppression by the Skaarj. Unfortunately the island holds a dark secret, an ancient deity has awoken and it demands a sacrifice. Unfortunate victims are drawn to the underground, never to be seen again. Unfortunately for you, you are about to become it's latest victim…






The mappack includes the following features:

• Five levels to explore, all set in different area's of the underground ruins below the island.
• Two hub maps to explore, including the island itself and the island port-town.
• Two new weapons added to the classic unreal weapon arsenal, including a crossbow grapple gun and a homing throwing-blade.
• Various new enemy types, including unique Krall classes, the War-dogs, and even malevolent Nali.
• Various NPC’s that you will meet on the way, each with their own narrative, unique quests and interactions.
• Upgraded graphical detail from the original unreal, using the new features and capabilities of the 227J patch.
• A narrative driven campaign, using character interactions, translator messages, and dream sequences to propel the plot forward, will you be able to discover the island’s dark secret and escape The One?

[Leo T_C_K]

Thanks and congrats for releasing this Turbo. I'll try it at the nearest opportunity. In fact I was also thinking of making a conversion for UT of this or just a semi-personal one for a coop server.

I suppose you'd be fine with that right? I know its meant to go with the 227 oldunreal patches, but if I make it clear its recommended to play/download the original then it should be fine I think.

[Leo T_C_K]

Unless you had a plan for a specific 469 version later down the road. I forgot if you had or not, I believe I talked to you years ago about this...

[Turboman.]

Hi Leo, no UT version is planned for this, I've considered the prospects of porting this to 226 or UT but it would seem a near impossibility without having to resort to removing a lot of things, it's a task that would be nearly impossible if you ask me, much alike to making a gameboy advance port of this mappack.

Closest thing I could do to make it 226 and UT compatible is to release the prototype version before I shifted development to 227, it's still not the same as the final version but that's something which I might consider doing if the community is interested enough in such a version.

[Leo T_C_K]

Hi Leo, no UT version is planned for this, I've considered the prospects of porting this to 226 or UT but it would seem a near impossibility without having to resort to removing a lot of things, it's a task that would be nearly impossible if you ask me, much alike to making a gameboy advance port of this mappack.

Closest thing I could do to make it 226 and UT compatible is to release the prototype version before I shifted development to 227, it's still not the same as the final version but that's something which I might consider doing if the community is interested enough in such a version.

I am interested. Well you can ask on UnrealSP.org as well or other places you posted this. Not much forum activity here though, may I suggest also asking on ut99.org. The Singleplayer section has Unreal stuff as well though they consider 227 stuff offtopic iirc, but if you tell them about this I am sure some people will get interested.

Also I am sure I could pull off the UT conversion one way or the other but as you said it would be a Lite version basically. With lots of workarounds and everything, like staticmeshes replaced with movers and regular meshes (plus hacks like xmesh) and possibly one of the custom particle engines and what not. I am sure that could be put together but it would be different.

Working on the UPSX project and others has taught me a lot of tricks used in different points and different situations, some of them no longer necessary but I could see applying some of them here. Some of the code references would need to be changed also, the magbow mechanics in particular will be tricky but it can be done still as long as its used "little differently". I have not examined this yet in details, but I can already tell you this.

[Hellkeeper]

I'm planning on playing this when I get the time, the screenshots are so sweet.

[BIr4]

Increnible.

[Leo T_C_K]

Hi Leo, no UT version is planned for this, I've considered the prospects of porting this to 226 or UT but it would seem a near impossibility without having to resort to removing a lot of things, it's a task that would be nearly impossible if you ask me, much alike to making a gameboy advance port of this mappack.

Closest thing I could do to make it 226 and UT compatible is to release the prototype version before I shifted development to 227, it's still not the same as the final version but that's something which I might consider doing if the community is interested enough in such a version.

here's some feedback already on ut99.org forums:

https://ut99.org/viewtopic.php?p=139384#p139384

[.:..:]

Here's the beginning of the map pack in a new perspective!

[Leo T_C_K]

Here's the beginning of the map pack in a new perspective!

Absolute peak greatness LOL. My favorite mod really.

This should be now the canon trailer. "Hang in there, hang in there"

I assume glitchreal still is compatible with 227J?

[BIr4]

While playing I noticed something. I don't know if it's something to point out, but I think it's fixable. By the way great job.

[Leo T_C_K]

While playing I noticed something. I don't know if it's something to point out, but I think it's fixable. By the way great job.

It is fixable. But given how complex the map is, I'm not surprised it slipped by, besides maybe turbo isn't aware now that this might be easier to fix now with yrex's bsp tool. But there are still methods outside of that how to fix it/get around it.

normally the problem is that classically this requires/required a full rebuild to get fixed and it might introduce another issue somewhere else where it is not spotted. However, now that is not entirely true anymore because of the tool i mentioned or alternative tricks.