Has the Exult team ever considered creating a page full of the various usecode bug fixes made by the team and other members. Maybe actually include the download for usecode function 0495, to make it easy for other people to download and compile with the new usecode.
Would give me a place to put that liqueur fix too...
Or would this constitute too much of a legal risk for the team?
usecode bug fixes...
Forum rules
NOTICE: This forum is archived as read only.
Please use the Github Discussions at https://github.com/exult/exult/discussions
NOTICE: This forum is archived as read only.
Please use the Github Discussions at https://github.com/exult/exult/discussions
-
- Site Admin
- Posts: 1310
- Joined: Thu May 14, 2020 1:34 pm
Re: usecode bug fixes...
isn't this absolutely hilarious! I've actually made a page yesterday holding EXACTLY this information in the CVS tree.
Update your tree and look at docs/usecode_bugs.txt
Artaxerxes
Update your tree and look at docs/usecode_bugs.txt
Artaxerxes
Re: usecode bug fixes...
I read that page... so thats what got me thininking..
I thought it would be swell if the actual compiled .wuc file was available to download, along with a text fle explaining all changes made. This would make it really easy for anyone to share their usecode edtted bug fixes. Avoids the trouble of decompiling, editting, then compiling them again and in ensures that you don't muck up the editting process. And since the files are so small they'd be a quick and easy download and with an included text file a person can see exactly what changes were made.
I thought it would be swell if the actual compiled .wuc file was available to download, along with a text fle explaining all changes made. This would make it really easy for anyone to share their usecode edtted bug fixes. Avoids the trouble of decompiling, editting, then compiling them again and in ensures that you don't muck up the editting process. And since the files are so small they'd be a quick and easy download and with an included text file a person can see exactly what changes were made.
Re: usecode bug fixes...
oh yeah, on a side note, whats the command to actually save the files when you decompile with wud.exe I've forgotten how to save and I can't seem to find that info anywhere in the Exult CVS. I get a readout but I want to save as an independent file.
I mean, the Exult CVS is huge, its hard to find anything despite how well its organized.
I mean, the Exult CVS is huge, its hard to find anything despite how well its organized.
Re: usecode bug fixes...
Just redirect it into a file using >
wud [whatever options you need] > filename
wud [whatever options you need] > filename
Re: usecode bug fixes...
The fact that you need to use the ">" should really be included in the wud.exe instructions when you just run wud by itself.
Re: usecode bug fixes...
Why? This is just DOS syntax. wud has nothing to do with it.
Re: usecode bug fixes...
O.K. I hate to keep spamming your message board, but irc.openprojects.net seems to be down right now.
When I type,
"wud 04fa.uco 04fa.uc"
I get a full readout of the decompiled usecode, when I type,
"wud 04fa.uco > 04fa.uc"
the 04fa.uc file generated is always just a header file, 81 bytes.
I'm sure its something simple, but I'm not a programmer of any sorts.
When I type,
"wud 04fa.uco 04fa.uc"
I get a full readout of the decompiled usecode, when I type,
"wud 04fa.uco > 04fa.uc"
the 04fa.uc file generated is always just a header file, 81 bytes.
I'm sure its something simple, but I'm not a programmer of any sorts.
Re: usecode bug fixes...
It's irc.freenode.net now. (they changed their name)
wud also needs a function number argument, IIRC, or -a for 'all functions'.
So:
wud 04fa.uco -a > 04fa.uc
The reason 'wud 04fa.uco 04fa.uc' works is probably because it's interpreting 04fa.uc as the number 04fa.
wud also needs a function number argument, IIRC, or -a for 'all functions'.
So:
wud 04fa.uco -a > 04fa.uc
The reason 'wud 04fa.uco 04fa.uc' works is probably because it's interpreting 04fa.uc as the number 04fa.