observed diffrences between urucc and mystv

[Sirius]

ORLY?

There is a difference between knowing how the PRP format is constructed and being able to make any meaningful PotS DLL.
We're in 2021 and the only fix for widescreen monitors is still a crappy Drizzle hack that's incompatible with Shards.

[Tsar Hoikas]

Let me clarify: we have reconstructed headers for TPotS. This was not hard to do since we first gained the offsets to implement proper readers. The headers aren't mine, so I can't share them.

[Sirius]

Ah, I understand better. I didn't know this was part of the reverse engineering effort.
I guess the decision to keep some of this quiet was natural given how Cyan and the community reacted to hackers at the time. (I guess even today there is a non-zero risk of Ubisoft/RAD game tools/Havok bitching about reverse engineering being done on code nearly two decades old...)

[Tsar Hoikas]

Exactly. 10 years ago, OP would have been raked over the coals for even daring to open this topic. It's good to see folks are still having fun tinkering, especially now that it doesn't ha e to happen in secret.

[jfmherokiller]

Exactly. 10 years ago, OP would have been raked over the coals for even daring to open this topic. It's good to see folks are still having fun tinkering, especially now that it doesn't ha e to happen in secret.

well, I could also say I'm doing this for preservation's sake. Wherein, I am reverse engineering parts of the game in order to allow the game to possibly more easily run in a browser tab using something like http://www.boxedwine.org/ while being hosted on archive.org

[jfmherokiller]

and heres the latest set of Uru stuff I was able to "reconstruct" a possibly basic form for "plPythonFileMod"

Code: Select all


/* 1600 */
struct plPythonFileMod
{
  plPythonFileMod_VTABLE_0_0000000000A5AD4C::vtable *vftbl_0_0000000000A5AD4C;
  _BYTE gap4[100];
  void *field_68;
  char *fModuleName;
  _BYTE gap70[4];
  int field_74;
  int field_78;
  _BYTE gap7C[8];
  int field_84;
  PyObject *field_88;
  int field_8C;
  int field_90;
  _BYTE gap94[12];
  void *field_A0;
  void *field_A4;
  int field_A8;
};

/* 1601 */
struct plPythonFileMod_VTABLE_0_0000000000A5AD4C::vtable
{
  int sub_6A8A10;
  int sub_401460;
  int sub_4847C0;
  int sub_4847B0;
  int sub_6A7F00;
  int sub_6A7F20;
  int sub_6A7F70;
  int sub_6A7F10;
  int sub_6AED10;
  int sub_6AEFF0;
  int nullsub_324;
  int nullsub_325;
  int sub_6AAC90;
  int nullsub_326;
  int sub_401490;
  int sub_4014A0;
  int sub_62B520;
  int sub_63AB10;
  int sub_4014B0;
  int sub_63A640;
  int sub_6AABE0;
  int sub_410B90;
  int sub_410BA0;
  int sub_6A8CF0;
  int sub_6AA3D0;
  int nullsub_327;
  int sub_6AA7A0;
  int sub_6AA960;
  int sub_6AEB10;
  int sub_6AEB40;
  int sub_6AEAE0;
  int sub_6AEAF0;
  int sub_6A7FC0;
  int sub_6A7FD0;
  int Concurrency::details::VirtualProcessor::GetMaskId(void);
  int Concurrency::details::InternalContextBase::GetProxy(void);
  int sub_6A8000;
  int sub_6A81C0;
  int sub_6A81D0;
  int sub_6A8200;
  int sub_6A89A0;
  int sub_6A89B0;
  int sub_6AEB60;
  int sub_6AEC40;
};


[jfmherokiller]

after alot of work this is what i have now

Code: Select all

/* 1609 */
struct __cppobj plPythonFileMod : plMultiModifier
{
  plPythonSDLModifier *fSDLMod;
  char *fPythonFile;
  plString fModuleName;
  hsTArray<plKey> fReceivers;
  _object *fSelfKey;
  plPipeline *fPipe;
  hsTArray<plPythonParameter> fParameters;
  _object *fModule;
  _object *fInstance;
  bool fLocalNotify;
  bool fIsFirstTimeEval;
  bool fAmIAttachedToClone;
  PythonVaultCallback *fVaultCallback;
  pfPythonKeyCatcher *fKeyCatcher;
  hsTArray<plPythonFileMod::NamedComponent> fNamedCompQueue;
  _object *fPyFunctionInstances[39];
};


It is incorrect but close enough to be usable.

The types you see came from viewtopic.php?f=114&t=6113 I had to use a prebuilt version because trying to compile plasma myself seemed to cause a BSOD.

[Chacal]

I sure had fun doing that kind of things from about 1983 to 2008, on IBM mainframes, Commodore 64, Apple IIe and finally the PC.
Writing a disk-sector editor for removing copy protection from games on floppies. Writing a print server in assembly language. Doing things on the mainframe that the IT guys really didn't like. A few scripts for tinkering with Uru and other games.

But I'm afraid my tinkering days are over. But my 12yo son has started hacking...

[jfmherokiller]

due to personal things Im not sure when or if I will get back to this so I'm uploading everything in one piece. The Idb files in the archive are from ida pro 7.6
It contains header files, map files and pdbs as well.

the data is located at https://ipfs.io/ipfs/QmRkWzfr4bxQCtGz9E ... J4D48i2NyE

and to get access to the data you need 3 pieces of info.

Youth is like a seed.
All things must come to pass

to enter you must lower your expectations.

[Maroonroon]

due to personal things Im not sure when or if I will get back to this so I'm uploading everything in one piece. The Idb files in the archive are from ida pro 7.6
It contains header files, map files and pdbs as well.

the data is located at https://ipfs.io/ipfs/QmRkWzfr4bxQCtGz9E ... J4D48i2NyE

and to get access to the data you need 3 pieces of info.

Youth is like a seed.
All things must come to pass

to enter you must lower your expectations.

Seriously?
Why to share something with everybody and put a password with this kind of "info"?
I'm sorry, but it's stupid.
You can write the password typing "p a s s w o r d" in your post if you don't want "bots" to read/understand it, but anyway, it isn't the NSA data!
It looks like a troll to me.