[Barton Waterduck]

GTA SA PS2 MB v0.33 released.

http://home.tiscali.no/donkey99/SA-MB033.zip

New stuff in version 0.33:
- Proper support for custom global variables and arrays
(because the new memory system has finally been debugged).
- Setting up an array at address 0 didn't work. Fixed.
- New label format in decompiler.
- Decompiler now supports custom label names.
- Custom global variable names removed from the 'sascm.ini'
and put in 'variables.ini' with a new easier format.

New stuff in version 0.32:
- Opcode parameter definition 't%' in the 'SAscm.ini' file was changed
to use objects from the 'default.ide' file only while 'o%' is used
with any objects.
- Named references to the second segment objects added.
- Original mission titles added to hardcoded mission descriptions.
- Some cosmetical bugs fixed. :-)

--------------

GTA Vice City Mission Builder v1.41 released.

New:

CODE

DEFINE OBJECT BARREL4; object number irrelevant now ... 0107: $898 = create_object #BARREL4 at  284.3 -312.4  10.9

more in the readme. Links in my signature.

This post has been edited by Barton Waterduck on Tuesday, Jan 18 2005, 08:16

[kuchar]

QUOTE (Barton Waterduck @ Nov 15 2004, 18:20)

This thread is for all future version of my Mission Builders for GTA San Andreas, PS2 and PC versions. I'm currently working on support for the external scripts. I started with decompiling/disassembling the scripts in the 'script.img' to separate files. I ran into several practical problems and decided to decopile everything into one huge text file. All the missions have always been in one huge file anyway and it's easier to search for codes this way. Two unknowns left. One in the beginning of the memory and one in the external script 'aaa.scm'. I'm guessing it has something to do with the variable string space since the first 4 bytes in this file is the size of the "usual" memory. Or it could be related to memory in the external files. I will try to track it down tomorrow. New stuff: GXT reader. The GXT keys are coded in San Andreas. I used some code dans made for that. And a fully automatic internal IMG tool.

Did you do a gxt reader for SA?

[Barton Waterduck]

Version 0.3 released.

New stuff: GXT reader, automatic IMG tool to extract the scripts in the "script.img" file, "credit" files from GTA VC added, opcodes searching features brought back.

Known issues: Use a desktop resolution of 800x600 or higher. If lower, the
"open file" and "select destination path" dialog box will be too big.

Bugs fixed: Most of the 2nd segment object names didn't show up in the decompiled code in versions 0.1 and 0.2.

The math system used to code math related stuff without specifying the opcodes does not support arrays or local variables in this version.

Much more info in the readme.

[Y_Less]

When you recompile, does it put the other scripts back in the separate file?

[Barton Waterduck]

QUOTE (Y_Less @ Nov 16 2004, 21:46)

When you recompile, does it put the other scripts back in the separate file?

Yes, it recreates the "script.img" file. The "main.scm" and "script.img" file is recreated in the work/project/destination directory where the tables and "main.txt" file is. If you use "save as" on the "main.txt" the work/project/destination directory changes automatically and you get a messagebox asking if you want to copy the tables to the new work/project/destination directory.

[Barton Waterduck]

Version 0.31 released.

This is like a bug-fix to version 0.3.

New stuff in Version 0.31:
- Main scripts with empty segments can now be decompiled and recompiled.
- A debug message has been removed.
- Some tiny potentional bugs removed.
- Math system complete. CyQ found the new math codes.

Code tested with the new math system using the compiler and decompiler. Opcode 08FA could be wrong. The code has not been tested ingame:

CODE

if  0  $728($727,32i) ==  0  $728($727,32f) ==  0.0  $728($727,32s) ==  'test'  $728($727,32v) ==  "test" jf ££Label0146EB if  0  @728($727,32i) ==  0  @728($727,32f) ==  0.0  @728($727,32s) ==  'test'  @728($727,32v) ==  "test" jf ££Label0146EB $1735 = $760($727,32i) $1735 = $760($727,32f) s$1735 = $760($727,32s) v$1735 = $760($727,32v) $760($727,32s) = 'test' $760($727,32v) = "test" s$1735 = 'test' v$1735 = "test" @1735 = $760($727,32i) @1735 = $760($727,32f) s@1735 = $760($727,32s) v@1735 = $760($727,32v) @760($727,32s) = 'test' @760($727,32v) = "test" s@1735 = 'test' v@1735 = "test" $728(1) = 123; same as $729 when DMA support enabled $728(2) = 234; same as $730 when DMA support enabled $728(3) = 345; same as $731 when DMA support enabled Same code decompiled: 00D6: if  0 0038:   $728($727,32i) ==  0;; integer values 0042:   $728($727,32f) ==  0.0;; floating-point values 05AD:   $728($727,32s) == 'TEST';; 8-byte strings 08F9:   $728($727,32v) == "TEST";; 16-byte strings 004D: jump_if_false ££Label0118A1 00D6: if  0 0039:   @728($727,32i) ==  0;; integer values 0043:   @728($727,32f) ==  0.0;; floating-point values 05AE:   @728($727,32s) == 'TEST';; 8-byte strings 08FA:   @728($727,32,3) == "TEST";; 16-byte strings 004D: jump_if_false ££Label0118A1 0084: $1735 = $760($727,32i);; integer values and handles 0086: $1735 = $760($727,32f);; floating-point values only 05A9: s$1735 = $760($727,32s);; 8-byte strings 06D1: v$1735 = $760($727,32v);; 16-byte strings 05A9: $760($727,32s) = 'TEST';; 8-byte strings 06D1: $760($727,32v) = "TEST";; 16-byte strings 05A9: s$1735 = 'TEST';; 8-byte strings 06D1: v$1735 = "TEST";; 16-byte strings 008B: @1735 = $760($727,32i);; integer values and handles 0089: @1735 = $760($727,32f);; floating-point values only 05AA: s@1735 = $760($727,32s);; 8-byte strings 06D2: v@1735 = $760($727,32v);; 16-byte strings 05AA: @760($727,32s) = 'TEST';; 8-byte strings 06D2: @760($727,32,3) = "TEST";; 16-byte strings 05AA: s@1735 = 'TEST';; 8-byte strings 06D2: v@1735 = "TEST";; 16-byte strings 0004: $728(1) =  123;; integer values 0004: $728(2) =  234;; integer values 0004: $728(3) =  345;; integer values

This post has been edited by Barton Waterduck on Wednesday, Nov 17 2004, 16:12

[Barton Waterduck]

Did you know that the PS2 version of GTA SA supports running it from a PS2 harddrive ? I guess it wouldn't make modding PS2 games automatically legal, but if you never mention it to anybody, who is going to know anyway ? And it's not like Rockstar is going to loose any money on it, not that much anyway. And you don't even need a modded PS2 to do this. Been wondering about these legal matters because of my PS2 Mission Builders. Wonder if Rockstar know about this builder. I have known about this for some time now (like several days) and I wasn't sure if I was even going to mention it like this. Oh well, I'm just a nervous geek I guess. What do you people think ? Should we be discussing SA mission script codes now or should we wait until the PC version is out ? Or should we just mod silently in the dark ? Maby I even risk getting banned for posting this. Also, since I'm already writing stuff, I've been posting about this MB on several other forums and most of them are deleted by moderators saying my tool is illegal. That doesn't make things better. What I'm trying to say is that who on earth can keep a secret as big as this ? Not me anyway. We're talking about modding THE ps2 game of all times here and the retail version of it is actually moddable using any unmodded ps2's out there (except perhaps the new V12 version). All you need is a harddrive (40 GB to 120 GB (or higher with some unofficial patches)). I guess this post is long enough now.

[Opius]

It's fully legal Barton. Don't worry.

Besides, it's not like anyone can tell you you can't do something to a game you own, on a console you own, with modifications you've made yourself.

Well, there's the DMCA, but that's outside the scope of this argument.

[sleeper777]

I had many of the same thoughts BW when i saw articles about your software on other sites but no mention of the fact that these version were PS2 builders so i made it clear to them that the builder(s) should now have a platform(PC or PS2) Notation added to the downloads. or they should just direct all traffic to your pages....

I have a friend who is using his HD to mod a couple of other PS2 games. Not sure which ones but i agree with opius you bought it, you own it, you changed it..... no problem.....

[MarD]

Heyyo,

I agree, it's free, so it's legal. This's how 3rd party software/mods work in general: it can use parts of the original game and can be given to others AS LONG AS IT'S NOT SOLD FOR PROFITS. So since your mission builder is free, and doesn't include a whole pirated version of the game? it's legal, you have a tool for creating images yes, BUT it requires the user to already HAVE the game, further proving this program is legal. Hey, if R* diddn't like what we're doing? I'm sure they'd have stopped us by now, even they probably know aboot what we're doing.

I've got a great example of a company SUPPORTING a 3rd party mod, and I believe they actually sell their product too! and that's the machinima stylings of the series known as "Red Vs Blue: the chronicles of blood gultch." They use like, all aspects of Halo, and now? even Halo2, and Marathon (w00t! Marathon's free software, so you can download it, and mod it as you see fit and it's all legal! Also, Abuse is freeware! so dl that, n' start up a 2D side-scrolling shooting fury! )

So yeah, Bungie diddn't shut down RvB, they supported it. R* may not have been so supportive of what we do, but they seem just as nice as Bungie since they're givin' out some classic games for free (GTA1's freeware... ok, it's not free software like Marathon1 with complete source codes, but it's still cool).

Don't worry aboot those other sites/forums, they're just paranoid dude, and don't truly support the modding community.

So BW? I say dude, keep going. The further you improve your mission builder while the PS2 version's out, the better the PC version will be.

[PlatinumSerb]

I thought only a few things were modable on the PS2 version. Is the Mission Script one of them?

[Craig Kostelecky]

I don't think anybody's successfully changed anything yet (or if they even tried). Not many people have the HDD to test this.

[Y_Less]

You could use a ROM, but I think that may be illegal.

And yes, there are lots of exmples of companies supporting mods (Counter strike/ gunman chronicles for one (two)).

Just because Rockstar don't support the moding scene (and, as I understand it, they have covertly supported it a bit at some points), but they don't hate it. they said the files were free to be modded, so mod them. I don't think this could have gone un-noticed, especially with a community this big on the biggest gta site, and with all the publicity of myriad islands and LC.

If they didn't want it, they'd have stopped it LONG ago.

[Barton Waterduck]

QUOTE (Craig Kostelecky @ Dec 3 2004, 01:43)

I don't think anybody's successfully changed anything yet (or if they even tried). Not many people have the HDD to test this.

The only people I know of that have successfully modded the mission script using the MB with a PS2 harddrive is some moderators and administrators at the norwegian gta forum http://www.gtaforum.no
It's also the only forum I know of in addition to this (or these) that doesn't have a problem with the MB's existens. I guess the reason is that they already knew all about gtaforums.com and my mods before I released my MB there. I also guess they respect me more because I haven't gone bonkers there yet.

This post has been edited by Barton Waterduck on Saturday, Dec 4 2004, 14:03

[Y_Less]

[offtopic]

QUOTE

I also guess they respect me more because I haven't gone bonkers there yet.

I don't think thats something to be proud of or joke about. Alot of other people have been complaining about you recently, I don't like to take sides or say stuff, especially as I'm still quite new here, but I have to say i've noticed it as well and it aint good, especially when you start making fon of it

[/offtopic]

[Barton Waterduck]

GTA Vice City Mission Builder v1.41 released.

New:

CODE

DEFINE OBJECT BARREL4; object number irrelevant now ... 0107: $898 = create_object #BARREL4 at  284.3 -312.4  10.9

more in the readme. Links in my signature.
And I could have tested it more but I think it works (been playing half life 2 and counter strike (against the cheaters)).


This post has been edited by Barton Waterduck on Sunday, Dec 5 2004, 18:40

[Barton Waterduck]

I have decided to take down my GTA SA PS2 Mission Builder from my homepages since Rockstar regards any PS2 modding tools as warez tools. I have done this mostly to prevent my homepages from being taken down by my ISP's and possibly loosing my ISP's accounts. If modifying the game isn't against the forum rules at this time, I'm sure it will be pretty soon. This doesn't mean I have given up on modding my own version of the game. It simply means I can't release anything to the public. If any of you are still interrested in my work, just send me a PM and I will see what I can do.

[Barton Waterduck]

Anyway, since nobody got any "serious issues" with my SA mission script mod, here's a link to the old v0.31 GTA SA Mission Builder:
http://home.tiscali.no/donkey99/SA-MB031.zip

[Barton Waterduck]

News: Been working like the retard I am (and I'm not just saying, it's my hobby) on my GTA SA Mission Builder. It now has easier to read labels like

CODE

:Two_Player_Thread 03A4: name_thread 'TPLAYER' :TPLAYER_2 0001: wait  75 ms 00D6: if  0 0256:   player $PLAYER_CHAR defined 004D: jump_if_false ££TPLAYER_237

and what I posted, an ini file for custom labels (in addition to these automatically generated ones)

[Barton Waterduck]

fidrouple posting (spelling ?)

OK, if anybody is interrested in helping me with the new 'customlabels.ini' and 'variables.ini' you could probably need the newest version of the SA MB.

GTA San Andreas, PS2 version, Mission Builder v0.33:
http://home.tiscali.no/donkey99/SA-MB033.zip

New stuff in version 0.33:
- Proper support for custom global variables and arrays
(because the new memory system has finally been debugged).
- Setting up an array at address 0 didn't work. Fixed.
- New label format in decompiler.
- Decompiler now supports custom label names.
- Custom global variable names removed from the 'sascm.ini'
and put in 'variables.ini' with a new easier format.

New stuff in version 0.32:
- Opcode parameter definition 't%' in the 'SAscm.ini' file was changed
to use objects from the 'default.ide' file only while 'o%' is used
with any objects.
- Named references to the second segment objects added.
- Original mission titles added to hardcoded mission descriptions.
- Some cosmetical bugs fixed. :-)

The 0.32 version was never released (I think).

Don't use the 0.31 version or earlier versions. They should never have been released.
They don't handle any custom global variables correctly.

This post has been edited by Barton Waterduck on Monday, Jan 17 2005, 09:52