Castle Paradox

[Aethereal]

Since you're the *ahem* plotscripting master here, mind helping me out with some big time errors I'm getting in my script?

94,atk: Attack9
constant atk:attack9 will be ignored because it is already defined in line
344 of magis.hsi with the value 77

WARNING: in line 362 of magis.hsi
95,atk: Attack10
constant atk:attack10 will be ignored because it is already defined in line
345 of magis.hsi with the value 78

WARNING: in line 363 of magis.hsi
96,atk: Attack11
constant atk:attack11 will be ignored because it is already defined in line
346 of magis.hsi with the value 79

WARNING: in line 364 of magis.hsi
97,atk: Attack12
constant atk:attack12 will be ignored because it is already defined in line
351 of magis.hsi with the value 84

parsing top-level
ERROR: in line 13 of skillset.hsi
define script (autonumber, skillset_deros, none)
Expected number but found autonumber

The one that really gets me is the last one, because I made that .hsi, and so why would it expect a numbered script?
_________________

[Fenrir-Lunaris]

Hmmm... I used to get something eerily similar to that when making FFH. Couldn't figure out what was causing it though, and it didn't seem to have any undesirable effects.

[MultiColoredWizard]

Does it have anything to do with XP?

[Cube]

The the first bunch of errors:

This is happening because you're redefining constants. Like this:

WARNING: in line 364 of magis.hsi
97,atk: Attack12
constant atk:attack12 will be ignored because it is already defined in line
351 of magis.hsi with the value 84

This means that on line 364 you're trying to change the value of the variable Attack12 to the number 97. However on line 351 you've already made the constant and gave it the value 84.

But what does it all mean? It means that you cannot redefine constants. That's why they're called constants after all...They are a certain value CONSTANTLY and FOREVER. They cannot be changed, so you will have to resort to global variables or make a lot of functions with local variables to do what you want.

However, if you're including the hsi file that was exported from your game, you should know that the file is just a bunch of constants. You may be trying to make a constant variable that has the same name of an attack.



Now, for the last error I'm not sure YET. I need to know more information and stuff, like how it's used, where it's defined and so on.

[Aethereal]

For that error...umm, I never define my own constants (don't have a reason to, as I don't have horribly complex plotscripts) and magis.hsi is the exported hsi from CUSTOM. :
The other error...I'll have to paste a few things directly from my scripts.

SKILLSET.HSI:

#-----------
#Definitions
#-----------

define script (autonumber, skillset_deros, none)
define script (autonumber, skillset_katalin, none)
define script (autonumber, skillset_aden, none)

#-------
#Scripts
#-------


#--------------
#Skillset_Deros
#--------------

script, skillset_deros, begin

if(check equipment(find hero(hero:deros), slot:weapon) == 1) #Long Sword
then(
writespell(find hero(hero:deros), 0, 0, 21) #High Blade
)
if(check equipment(find hero(hero:deros), slot:weapon) == 9) #White Sword
then(
writespell(find hero(hero:deros), 0, 0, 21) #High Blade
)

(it goes on with more stuff identical to that)

MAGIS1.HSS (my main plotscript file)

#----------------------------------
#Skillset Script. See skillset.hsi.
#----------------------------------

define script (1000, skillset, none)

script, skillset, begin
skillset_deros()
skillset_katalin()
skillset_aden()
end

Script 1000 SKILLSET is used as an "each-step" script on the map so it is always running the various SKILLSET_CHARACTER scripts defined in the .hsi. I'm sure it doesn't have anything to do with the fact that I'm using a handmade .hsi in my compilation, because Moogle did that with OHR Tactics in a similar manner.
_________________

[Me]

I hate the tab key. Continuing . . .
If you have the include, whatever.hsi command ( whatever being the name of your game, thus this "includes" your game's constants), make sure you don't have the same command in your extra hsi file (that is, the one with the autonumbered scripts). If you have this, the compiler reads the included files first, and thus thinks you are double defining constants. I encountered this problem when building my own "extra scripts" file.
Conclusion: Your included files don't need to include your constants. Constants only need to be included in your main file.
_________________
UP DOWN UP DOWN LEFT LEFT RIGHT RIGHT A B START

[Aethereal]

Reviving dead threads is quite evil, but I figured out the problem with James' help. The problem was not the reason you stated :\ If you want to read that thread, it's here: http://members.boardhost.com/OHRRPGCEHelpMe/msg/15741.html
_________________