Kpt 1988

Multiupload.com - upload your files to multiple file hosting sites!

=D

idk what this game has in special, if anyone knows, please tell us.

Does this exe still include XTrap (© WISELOGIC Co. Ltd) code?

AFAIK the last big introduction was the Phoenix pet which came around 1965 and then the additions of the ET3 dungeons around 1970. (or, re-introduction... since they seem to be old data that was always supposed to be there, but put off for reasons unknown)

Regular Test clients have been coming out of KPT again for some time now, but little has been dramatically changed... rather like there was little of interest from 1855 to around 1895 when the Smelting and Metallurgy NPCs where added.

These are only rough guestimates.

I wouldn't be surprised to find the item tables and premium (temporary) armours changed... Oh, I also heard they where Beta testing re-introduction of the nProtect / GameGuard (now both produced by the same company, INCA Internet) protection system in place / alongside XTrap.

this game.exe doesnt have metion of NPROTECT. And, in fact, it has ET3 and S3.

I cant remeber now if I removed xtrap... >.<

But, this isnt a beta client.

Err... yes it is, or it's no v1988, one or the other.

The Release clients from KPT start at 22xx, and the present is around 2352... all the 17xx, 18xx & 19xx are the Test versions... where they beta new features.

It's odd that it doesn't have any nProtect information, as 1977 still has "WWW.NPROTECT.COM" @ 005C6510, and the code completely bypasses it. XD

this KPT 1988 isnt beta, right? It is like QF 1873?

QF1873 was a modification of KPT 1872 which was a KPT Test client.

Some confusion may be that I'm "mixing metaphors", or rather applying standard U.S. IT&HE industry terms to a Korean product for which they have their own development cycle and terms they apply to the various stages within that cycle.

They say "Test". The term "beta" indicates in a software / hardware product which is in a usable state, has passed all internal "alpha" testing (debug, component test data cycles, regression testing and profiling) and only requires large scale (l)user play-testing by actual users.

In other words, you've thrown everything at it in the lab that you can possibly think of, but you still know full well that a couple of thousand actual people who don't have the slightest idea how the thing works inside will find at least 50 things you hadn't considered. :wink:

So what KPT call a "Test" client and "Test" server, I think it's fair to translate as "beta". If your opinion is different, then I apologise for the confusion.

To be clear about how the PT developers consider their development cycle, they do have specific codes (below 1000)for "in-house" betas, which are essentially post "alpha" out of Debuging and so-on which they call "beta" but would better fit the term "pre-release" or "closed beta" versions, similar to the "Longhorn" Betas which where available to a relatively small number of reliable beta testers among organisations in the official "Microsoft Partnership Program"... as opposed to the Betas of Vista (same product re-branded closer to it's release) which where widely available as time-limited trials for anyone who signed up to Microsofts' Beta test program to download and use for the duration of the trial.

So, to explain that analogy, any KPT client with a version below 1000 is like a Longhorn beta, any version number below 2.00.0 is like Vista betas, and anything 2.00.0 and higher is like the "stable" Retail (or RTM, Released To Manufacturers / Mass-production) version. From my perspective. :wink:

Some FOSS development teams keep "Stable", "Stable Beta", "Beta", "Pre-Beta" and "Alpha" branches of a product going simultaneously. They do this because they don't have massive copyright concerns or partnership programs with co-operating and interested multi-national corporations, just a community of many volunteers with widely differing levels of experience and areas of expertise. In that line, KPT 1xxx versions are a "Stable Beta" KPT < 1000 is just "Beta" and > 1999 is just a "Stable" release. I'm fairly certain that the PT developers don't assign a version, but maybe just a build number to anything at levels equivalent to "Pre-Beta" or "Alpha" developments.

From the way I work, what I call "Prototyping" or a "Prototype" release is "Alpha" to "Pre-Beta" level. If I say my work is a "Beta" I mean it does everything I expect it to, in exactly the way I expected it to do it and I've proved all of that... but I don't know what you might want to do with it, and if you do something I hadn't considered, I have no idea how it may react. :wink: I will only call something a "release" when I know several people have tried using it in various different ways, and I've ironed out any difficulties for any of these implementations. (I don't make a lot of "releases", but I rarely get as much "beta" feed-back as I'd like) :wink:

From the official KPT development teams' point of view, they might like to know, from their "Test" version, what happens when someone tries playing the game on their Tablet PC with no keyboard or mouse... or what happens when they try to run it on an EEE PC that throttles the processor as soon as it's expected to do any actual work, or how it responds when a disabled person with motor-neuron disease tries to play with their tongue-stick as the only input device. As well has how many new hacks are found that can take advantage of new features they are considering implementing in the "stable" server, before those hacks wreak havoc on the economy of the stable server.