Golden Sun Hacking Community
December 06, 2019, 09:09:04 AM *
Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
News:
 
  Home   Forum   DC Wiki Help Search Calendar Downloads Login Register  
Pages: [1]   Go Down
  Print  
Author Topic: Class and ability system implementation ideas  (Read 3587 times)
0 Members and 1 Guest are viewing this topic.
Misery
Bad Luck

Great Member
***

Coins: 0
Offline Offline

Gender: Male
Clan Position: Mercury Hack Leader
Posts: 714

« on: June 09, 2019, 03:51:45 PM »

Here are some suggestions for how to build Golden Sun's class system in a way that circumvents some design/functionality limitations imposed by the original methods. They're mainly aimed at those who want to make or are working on GS fangames or other GS-based games, though GSHC still seems like the most suitable place to put it on and refer to. And there's nothing stopping you from hacking this into the original games, although that may not be the most practical...

I'll start with the "how" and touch a bit on the "why" as I go. Occasionally I will refer to the original methods, but I don't think it's necessary to be familiar with them in order to follow this. The concept of elemental levels (may be abbreviated as eLevel) is still central, these can practically be thought of as the amount of djinn a character has equipped (set), e.g. one Mars djinni would add one Mars level. And in case anything is unclear, or if you think these ideas are bullshit or don't work, I'll have a Q/A section at the end.

It should be noted that the algorithm for assigning classes would be functionally identical to what it is in the GS series, only the arguments differ. Perhaps the main distinction is that originally, each entry in a class "line" has their own data set, whereas this will be based around the idea that each class is treated as a single object, with parameters (stats and abilities) that improve with higher eLevel.

Class data table
  • Elemental level requirements
  • Stat modifier table
  • Ability table
  • (Class name list)
  • (Effect vulnerability list)

Each playable character would have 4 accessible class IDs assigned to them, with the one to actually be used being determined by which of their eLevels is the highest. They would also have a list defining elemental prioirity in case of ties. Consequently all of their potential classes can be either entirely unique or shared with other characters on a case by case basis.

Class IDs:
  • Venus level highest
  • Mercury level highest
  • Mars level highest
  • Jupiter level highest

Elemental priority value:
  • Self = 4
  • Opposite = 3
  • Neutral = 2
  • Affinity = 1

Opposite: Venus to Jupiter, Mercury to Mars
Neutral: Venus to Mercury, Mars to Jupiter
Affinity: Venus with Mars, Mercury with Jupiter

To determine which class ID should be used, do [(eLevel * 5) + priority] for each element and use the element which gets the highest resulting value.

The class ID refers to a list of classes, or just a single class as may often be the case with base classes. Once the ID is obtained, check each entry of that list until one meets the eLevel requirements, that class then gets assigned to the character. Entries should be ordered so that classes with higher eLevel requirements are checked before those with lower.

This method removes two quirks from the original system, the first being that classes with lower eLevel requirements could override those with higher, the most prominent example being base classes - add one djinni of any other element, and suddenly you're in a tier 1 class even though you have enough djinn for tier 5. The other one is "spillover" classes which could result from an element with a level of 6 or higher effectively being treated as the character's primary element. Though if one still wanted that functionality, it could be recreated and designed for in this system.

Originally, characters start with 5 base eLevels (no djinn equipped) of their own element. This system assumes they do not, and as such, the djinn requirements for tri-elemental classes would have to be changed a bit if you want them to be "truly" shared between characters, i.e. to avoid defining the class twice with different eLevel requirements. More specifically, they would need to have eLevels (djinn) of their own element in addition to the other two. On the flip side, this does offer the option to do that for some slight class variations while still sharing the same ID (group).

Edit: another workaround to enable shared tri-elemental classes would be to either add the 5 elemental base levels but disregard them when checking highest element, or to add them only to the check for class requirements. Both of those options would require the base element to be defined in the character data.

Stat modifier table
Two values would be defined for each stat, base modifier and eLevel modifier. The actual modifier for a given stat would be obtained by [baseMod + (eLevelMod * total eLevel)]
In other words, each equipped djinni, regardless of element, would contribute to the stat modifiers as defined on a per-class basis. This has the benefit - or drawback - of enforcing a more even stat scaling based on djinn equipped, you do not get the jumps of the original system.

An alternative that would be similar to the original mechanics is to instead refer to a table where each entry is a set of stat modifiers, and where the entry to be used corresponds to total eLevel (+1 if not 0-inclusive). For the record, this is basically how Golden Sun assigns eLevel-based elemental power and resistance bonuses. This would enable the uneven scaling as seen in some classes.

Anyway, I believe that basing stat modifiers on total eLevel may help make class changing a bit less intimidating for players who are not very familiar with the system, as it grants stat boosts for each djinni equipped rather than having to conform to arbitrary element combination thresholds. It would also make changing classes in battle more tactically viable, same for using summons with multi-elemental classes. Which specific method to use is mainly a question of design philosophy.

Ability table
Each entry would have the following fields:
  • Ability ID
  • Level learned
  • (Element)
  • Min. eLevel
  • (Max. eLevel)

Basically, the advanced class abilities would require the user to have sufficient eLevel rather than being in a specific class tier. This also opens up some new opportunities, mainly that it allows classes to conditionally have abilities of elements they would normally be unable to use. That would also make it seem more like individual djinn grant additional abilities when equipped.

Element can optionally be defined to know which eLevel to check, or it could be fetched from the ability data.
Max eLevel can optionally be defined for "upgrading" abilities, e.g. Ragnarok to Odyssey.
One could even have fields for min/max requirements in all four elements, which would allow for compound elemental abilities (plasma could be wind/fire, growth could be earth/water, etc). Just a thought, probably not something I'd do personally.

Class name list
Class names have always been a design headache to me, having to come up with several different names for a role that is fundamentally the same is bound to result in some reaching on occasion. Nevertheless there is the familiarity factor, and one may want to use the names as a means to telegraph the increased mastery of a role. For these reasons, I'll include methods for having named class tiers that are compatible with this system. Even so, having 5 or 6 different names for the same class seems a bit ridiculous, surely it would be enough to have 3 for standard classes and at most 2 for complex, multi-elemental classes.

A simple method would be to just take the "main" elemental level of the class and use that to check a list of [value, name], where if eLevel >= value then assign name.

For stricter and more flexible naming, one could instead use a list of:
[Venus Lv, Mercury Lv, Mars Lv, Jupiter Lv, name], i.e. exactly how Golden Sun already assigns classes but used for names only.

Effect vulnerability list
This is a somewhat peculiar part of class data in Golden Sun that a lot of people probably don't know about. Basically, up to 3 effect values can be listed, which makes the class more susceptible to fail resistance checks against those effects. I figure if you wanted classes to actually have individual effect weaknesses and/or resistances, you could put a simple list here with [effect, argument]. The argument could be a multiplier or it could be used however you want really, it depends entirely on the implementation of effect/ailment resistance checks.

All that said, having this at all is highly optional - but if you do include it, at least display it somewhere on the character status screen so that players have a fair chance to be aware of it.

Q/A

Q: Just four classes per character? You could have much more than that in Golden Sun.
A: I have a feeling this might come up, so I'll address it right away. The class ID value is just part of the sorting method; tri-elemental classes are defined by their eLevel requirements but still have a primary element, such as the Ninja which is a Jupiter-based class that requires both Venus and Mars levels, or the Dragoon which is the same but Mercury-based.
« Last Edit: June 10, 2019, 06:02:08 PM by Misery » Logged
View Profile
Pages: [1]   Go Up
  Print  
 
Jump to:  

Cbox
December 04, 2019, 11:48:57 AM
Fox: (Uh... Ignore "Love" at the beginning... I think I started to say it in a different way, then changed my mind.)
December 04, 2019, 11:47:50 AM
Fox: Love gsiconcompressor has been updated... Mainly an attempt to make icon editing a bit more straight-forward than ever before. Although, the coding wasn't exactly that straight-forward.
November 14, 2019, 01:50:02 PM
Fox: So like... a layers offset might normally be located at +0xC, but in Tennis, it is at +0x10)
November 14, 2019, 01:48:51 PM
Fox: (Talking about the data in map header thingy.)
November 14, 2019, 01:48:10 PM
Fox: So took a look at Tennis.... Seems Atrius's editor displays all maps incorrectly because he forgot that some stuff was offsetted by 4 (You know with everything from layer offsets and files/etc.)  Fix that, and it seems to display properly. Hm.
November 14, 2019, 06:18:29 AM
Fox: That is a quote I found somewhere. How amusing. xD
November 14, 2019, 06:18:06 AM
Fox: only canadians give up dont be a canadian
November 11, 2019, 03:27:02 AM
Salanewt: Especially since there might be a v0.5.1.1 in the near future, if any bugs are found by people playing the demo.
November 11, 2019, 03:26:38 AM
Salanewt: Oh yeah, so for people who aren't aware; v0.5.1 of the AI Overhaul is available on the Discord, but I'm delaying the creation of a downloads page + topic until I finish the demo.
November 02, 2019, 12:05:31 PM
Fox: And yeah, there's a topic for the Discord. in News & Announcements (http://forum.goldensunhacking.net/index.php?topic=2831.0)
November 02, 2019, 11:55:00 AM
Fox: Went to go study some German a little earlier. (Using duolingo to give it a try.) ... And. Huh. German capitalizes all nouns? (Not necessarily pronouns, though.)
November 01, 2019, 07:49:25 AM
thenightsshadow: Didn't realize there was a Discord at all.
October 31, 2019, 07:22:02 AM
Fox: (Which I guess not having Special badges in inventory was by purpose.... So I'll ifnore that bit. Just whats with the dup Halloween badge in inv?)
October 31, 2019, 07:18:26 AM
Fox: Question about badges = Why do I have two of the same Halloween badge in my inventory... but not on my profile? And by two, I mean the Honk badge is not there.
October 31, 2019, 06:56:26 AM
Fox: Does tns want to join the most active part of GSHC? - Its Discord? :D  And welcome back!
October 31, 2019, 06:52:17 AM
Fox: (Ofcourse it would be capitalized if it were the name of a system, and anytime that system would be referenced... but I'm more going with why we *never* see Psynergy and Djinni not capitalized.)
October 31, 2019, 06:49:58 AM
thenightsshadow: Yeah, just kinda got an email out of nowhere and it reminded me.
October 31, 2019, 06:42:40 AM
Fox: and main reason I said "not intended to become part of English" ... was because I thought of words like "animals"... and they can technically still be lowercase at times.
October 31, 2019, 06:41:17 AM
Fox: group/type/thing/whatever
October 31, 2019, 06:38:54 AM
Fox: Not saying it is exacly that... but it is a thought, at least.

Affiliates
Temple of Kraden Golden Sunrise
Powered by MySQL Powered by PHP Powered by SMF 1.1.21 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!
Page created in 0.113 seconds with 22 queries.