Jump to content


c4_angel

Member Since 20 Mar 2017
Offline Last Active Apr 04 2018 01:28 PM

Posts I've Made

In Topic: Question to copy regexp

05 February 2018 - 10:33 PM

Thank you!

EDIT: Unfotunately, I came to a limit in file size with my planned PVRZ + tis approach. Your answer will be helpful nontheless.

COPY_LARGE?


In Topic: min level/max level in spells

25 January 2018 - 11:12 PM

Seems the mInimum level should be 0, as the "Holy Word" spell (sppr710) in SR.


In Topic: How to convert a string-like int variable to a real int variable?

15 December 2017 - 04:32 AM

Thanks to all of you.


In Topic: Toss your semi-useful WeiDU macros here

28 November 2017 - 04:55 AM

 

 

 

I made a table of all this here, excluding the values above 6240, as it varies depending on game version.

 

That's a great table. Thank you very much!

 

And I still may need help in two issues:

1. You mentioned "Spellstates 6240+ are dependent on the game campaign/version, read directly from specific offsets of the EXE. Pattern is 32(set) - 160(emtpy) - 32(set), and repeats semi-consistently up to the max (32767)". If I skip 6240-6271, use 6272-6431, then skip 6432-6463 ...etc, will function as expected?

 

2. Can I use splprot.2da to check them in script ? And how?

The semi-consistent part is that it occasionally has an extra multiple of 160 empty SPLSTATES between sets.  For example, BGSOD v2.3.67.3, starting from 6240, has:

3x(32 - 160 - 32) - 160 - 7x(32 - 160 - 32) - 1600 - (32 - 160 - 32) - (32 - 160 - 32) etc...

But I don't know if every game version has the same pattern off extra space or not.  I didn't go very far with it, other than to check from the other end (32767) to see if it was still in effect.  The second 32 of each such set has always had the exact same value though, 0x0000000a, using only bits 1 and 3.

 

SPLPROT only works in spells/items/projectiles, and comes with an entry for checking SPLSTATES, entry 110, using Parameter1 to specifcy the spellstate.

Scripts still have to use CheckSpellState().

 

 

a little confused with the pattern, but try start from 32767 will be a good idea, thank you.


In Topic: Toss your semi-useful WeiDU macros here

27 November 2017 - 09:40 PM

 

I made a table of all this here, excluding the values above 6240, as it varies depending on game version.

 

That's a great table. Thank you very much!

 

And I still may need help in two issues:

1. You mentioned "Spellstates 6240+ are dependent on the game campaign/version, read directly from specific offsets of the EXE. Pattern is 32(set) - 160(emtpy) - 32(set), and repeats semi-consistently up to the max (32767)". If I skip 6240-6271, use 6272-6431, then skip 6432-6463 ...etc, will function as expected?

 

2. Can I use splprot.2da to check them in script ? And how?