øAslickproductions.org/forum/index.php?PHPSESSID=5f0fck550j2m4m2fpbtkj2vkm1&action=profile;u=25;area=showposts;start=390e:/My Web Sites/Slick Productions - FFIV Message Board/slickproductions.org/forum/index90c6-3.htmlslickproductions.org/forum/index.php?PHPSESSID=5f0fck550j2m4m2fpbtkj2vkm1&action=profile;area=showposts;u=25e:/My Web Sites/Slick Productions - FFIV Message Board/slickproductions.org/forum/index90c6-3.html.zxI›h^ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÈà•¤"åOKtext/htmlISO-8859-1gzip@øÕ"åÿÿÿÿÿÿÿÿWed, 11 Mar 2020 08:19:45 GMT0ó°° ®0®P®€§²ð®H›h^ÿÿÿÿÿÿÿÿ*#"å Show Posts - assassin

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - assassin

391
Game Modification Station / Re: Need information on monsters
« on: October 22, 2014, 11:45:46 AM »
Quote from: dn
What is "8-high [and 16-high] composition data"?

if you're going to provide a quote, why not say where the hell it's from?

Quote
Also, is there anything actively preventing me from expansion? The game uses a byte in the monster data, I believe, to determine whether it's in the first 256 set (available to the Veldt) or the second set (which currently only has 128 entries, and which is what I want to expand).

some code (e.g. in Bank C2) will consider the monster to be absent if the low byte is 255 and the high byte is nonzero.  you'll have to narrow the high byte check to not rule out as much.

392
General Discussion / Re: NFL season 2014-2015 week 4
« on: October 15, 2014, 06:06:08 PM »
wow, it must be getting lonely in here. :sad:  but you're sure to run away with the regular season title. :happy:

393
Game Modification Station / Re: Magic condensing patch
« on: September 30, 2014, 09:37:47 PM »
his patches tend to work, but his bug description there is overly terse, and people who haven't played FF6j won't know what he's talking about.

1) if and only if you're missing three consecutive spells, the game will skip an entire row of menu output, so as to shorten the menu without changing the column of any given spell.  (thus keeping it easy to find for players scanning down the list.)
2) the condensing is done on a "union" list based off of the spells known by anybody in your active party.  so if Mog knows a boatload of spells, and Shadow traveling with him knows very few, the latter's list won't change much.

#1 is pretty desirable for players (once the patch changes it to two-at-a-time on FF3us, anyway).  i dunno how you'd change #2, short of finding a lot of free RAM to hold the separate lists, and reordering/rewriting a lot of code.

394
General Discussion / Re: Emergency
« on: September 25, 2014, 02:08:36 PM »
can you dump the SQL from mnrogar's as well, and send me a backup of that?  the last one i have is a few years old.

395
Game Modification Station / Re: FF6 Improvement Project
« on: September 18, 2014, 12:00:29 PM »
eh, i liked it better in 2010 without the GUI:
http://zephyr129.brinkster.net

396
Game Modification Station / Re: FF6: AI Upgrade bug help
« on: July 08, 2014, 12:14:47 PM »
ooh, very ambitious stuff.  i've thought for awhile that Nested IFs would be cool, but hell if i was gonna attempt it. :/  a computer science instructor would probably give you grief for "spaghetti code", but that beats writing some big parser/interpreter that has to do something like store states recursively.

Quote
For example, in my demo boss, he has a few actions he takes when the party has such-and-such statuses, but I don't want him to ONLY respond to the party statuses, so I can have him perform those actions and continue with his normal script.

something you can take advantage of in the normal game is that the failure of *any* If Test in an IF Block is enough to make things proceed afterwards like the whole block had been skipped.  take this pseudocode example:

-----
If real condition test
Fire
Ice
If BS-always-false condition test
End If

Bolt
-----

the "End If" isn't executed, per se, but found and branched past by the last failed IF, which means we don't exit the script.  anyway, thanks to Master ZED for this insight on script function.

397
Game Modification Station / Re: FF6: AI Upgrade bug help
« on: July 08, 2014, 12:41:05 AM »
that's a lot of different changes to your ROM.  try making a separate patch for each one, and applying them one at a time to figure out the culprit.

The last, is the fact that I wrote code to allow the scripts to run both inside and after conditionals optionally allowing me to queue up a bunch of attacks per turn. I'm worried that maybe I'm getting an overflow problem that is crossing over into graphical data.

yeah, this sounds like quite a significant change.  can you elaborate on what you're doing, and why you're doing it?  why not just have the script issue a bunch of commands per turn, like you mentioned for your test scenario below?

398
Pandora's Box / Re: PB Demo III findings
« on: July 02, 2014, 11:45:52 AM »
Quote
Gau's FF6A is no more descriptive than ours, except for implicating something sexual, potentially.

no, that'd be "Virile Child".

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

Quote
It seems to be when there are a lot of items in the inventory, or maybe it's a certain type of item(s), not sure.

doesn't the original game have a slight lag with large inventories as well?  or maybe i'm just thinking of Optimize in the Equip menu.

Quote
Or maybe it's all the new icons?

that could definitely impact things.  each icon type causes a 256-slot Item list to be iterated (albeit skipping most of the code for blank slots).

399
or you can do: AND #$00FF , XBA.  if you know the top half of A was already zero (e.g. a TDC right before the loading of APL), then just the XBA is needed.

400
3) AND #$FF00

AND #$00FF ?

Quote
This should serve to raise stats in a ratio very close to APL:Monster level

an interesting idea.. it depends on what you're aiming for.  this is vastly different than your initial algorithm.  if a level 40 party met a level 10 monster on that, the monster's level would become 22.  now, such an encounter would make the monster level 40.  which do you prefer?

another idea yet: if you have space, add an extra ROM field for each enemy: Level_Should_Be_Met_At .  this is subjective, but based on your and other players' experiences, you could come up with something.  if your party average is above that level, multiply the monster's level and stats by APL, then divide by Level_Should_Be_Met_At .

of course, if any of the stats are treated as squared in the damage formulae (e.g. Level in FF6 for physicals; i'm unfamiliar with FF4's equations), you'll get your head knocked off.  maybe temper it by lowering the ratio some..  i was gonna suggest square root of the ratio, but that'd be inhuman to code. :P  another way is to halve the part of the ratio that exceeds 100%: e.g. 1.60 becomes 1.30, 2.20 becomes 1.60, etc.  wouldn't be a picnic to program that either, but it's more feasible, and would limit how overpowered monsters get.

401
you're welcome.

it's an intriguing patch, though one problem i'm seeing with the algorithm is the potential for "leapfrogging".  suppose Average Party Level is 60, and a given monster also has a level of 60; it won't be levelled up.  but if a monster has a level of 59, it gets levelled up all the way to 88.

one way to avoid this is to not level up or boost any monster whose level * 1.5 would exceed adjusted APL, though this will lower difficulty a bit.

a more involved way would be to lower the level/stat multiplier from 1.5, depending on how far the enemy's current level is below adjusted APL.  so you'd do something like:

1) if monster's adjusted level >= adjusted Average Party Level, then exit.
2) tempLevel = monster adjusted level * 1.5
3) if tempLevel <= adjusted APL, then goto step 12.
4) find adjusted APL / monster adjusted level, giving quotient and remainder.
5) multiplier = (monster adjusted level * quotient) + remainder.
6) oldLevel = monster adjusted level
7) monster adjusted level = monster adjusted level * multiplier
8) each of monster other adjusted stats = each of monster other adjusted stats * multiplier
9) monster adjusted level = monster adjusted level / oldLevel
10) each of monster other adjusted stats = each of monster other adjusted stats / oldLevel
11) exit.
12) monster adjusted level = monster adjusted level * 1.5
13) each of monster other adjusted stats = each of monster's other adjusted stats * 1.5

(so Steps #2-13 are replacing your Step 5.)

this is a bit complicated.  and because you're multiplying before dividing (as that's needed to multiply by a mixed number of (multiplier / oldLevel)), you'll need a temporary 16-bit word to store the product.

402
Those $0042nn variables are custom SNES math registers.  Just set them, and it knows what to do. ;)  It takes several cycles, which is why the NOPs are there.  Mode-7 registers are another option for math, though I'm less familiar with those.  Yes, both of these should work on FF4.

403
Re #2: see how Square does it in FF3us function C2/4792 in the C2 disassembly:
http://home.comcast.net/~assassin17/guides.htm

404
Game Modification Station / Re: Code improvement
« on: March 18, 2014, 09:25:55 PM »
no; i'd thought that "But after looking again" meant you tried it out, so i wanted to know which emulator.

that said, your idea about the RAM dumps is good.

405
Game Modification Station / Re: Code improvement
« on: March 18, 2014, 06:09:31 PM »
Well it seems I have read fast but I saw yesteday this thread mentionning possible free ram in $144n and from $1508 to $1513. But after looking again, it seems those bytes are read from on a DMA transfer...

are you sure it's not the probable false debugger alarm i mentioned in that thread?  are you checking with Geiger, or something else?