Golden Sun Hacking Community
October 19, 2019, 11:59:09 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 2327 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
October 13, 2019, 04:51:53 PM
Salanewt: Oh, lol nice. :P
October 13, 2019, 04:44:28 PM
Fox: Maxi's already joined the server, he just never pops in.
October 13, 2019, 04:30:42 PM
Salanewt: I'll state up front that gsmagic has some overlap with the classic editor, but Teawater has been focusing on other things so you'll still want the original to do a lot of stuff.
October 13, 2019, 04:29:40 PM
Salanewt: As for moving posts over, I'll see if I can do it later today but I've been pretty busy these past few days.
October 13, 2019, 04:29:13 PM
Salanewt: Hey Maxi! I can help you with the latest "public" version of gsmagic if you join the Discord server, or when we start populating the board with topics, but if you want a download then you can go here: https://drive.google.com/drive/folders/1zZHTBD_7BTl6leXRgFulzSL9iS4TIBMt
October 13, 2019, 02:26:50 PM
Fox: Yes.  I am actually kind of surprised Salanewt hasn't moved my old GSMagic topic(s) over yet. (Even if they don't contain the latest versions.)  I have been focusing more on posting them to Discord. But it's been awhile since I've done any meaningful work, so....
October 12, 2019, 10:00:17 AM
MaxiPower: Any chance of getting a hold of the new editor for a test drive. Been here since day 1 (actually I was here since before there was a forum lol) so you can trust me.
October 07, 2019, 07:10:37 AM
Fox: It specializes in GS2, still... The others are just easter eggs because...similar formatting.
October 07, 2019, 06:26:27 AM
Salanewt: But it has GS1 editing and Mario game viewing/possible editing too.
October 07, 2019, 06:26:11 AM
Salanewt: That name made sense when it was just GS2 lol.
October 07, 2019, 05:02:04 AM
leaf: it's a better name than "the GSTLA editor" anyway
October 02, 2019, 08:13:00 AM
Misery: gsmagic is a fine name
October 01, 2019, 02:43:51 AM
Omx7: Heyo
September 29, 2019, 06:35:38 PM
Fox: Liking the changes so far.  In a way, I'm also wondering if I should give gsmagic a better name, since I see it has became a part of the Community, as I see by the board that has been added.... but... *shrug* - I can wait.  I still see it as an "experimental" editor.
September 28, 2019, 03:10:29 AM
zman9000: :)
September 25, 2019, 12:46:18 AM
Fox: Groovy.
September 25, 2019, 12:45:56 AM
Salanewt: Hey.
September 25, 2019, 12:23:19 AM
Megalord38: Hello, fellow Humans.
September 24, 2019, 11:18:49 PM
Salanewt: Yeah, baby!
September 24, 2019, 12:41:13 AM
Fox: Groovy?

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.115 seconds with 22 queries.