So I’ve been doing online Ruby courses, tearing through the FS3 Skill system, and watching a ton of YouTube videos in an attempt to create a simple skills system and I’m starting to feel like I’m spinning my wheels. I’m assuming I need more experience/knowledge with Redis? Based on what I’ve seen in the source code I can call up the big old list of attributes on a character but I can’t figure out how to plug a specific attribute field from that monstrous list of data. For instance, if I just want to see a character’s Grit and Grit rating.
At any rate, I have a vacation coming up which means I have almost 2 weeks to dedicate to nothing but figuring this out. My question here is, does anyone have any suggestions for any good tutorials that would help me out in this area? I continue to pour over the FS3 skill system but I won’t lie, it’s so sprawling that I have a difficult time tracking down specific information. And then, when I do, I have a difficult putting it all together.
Again, probably a lack of a proper knowledge base. If someone could give me a nudge in the right direction you’d be my hero. Thanks. 
Have you done the Ares coding tutorial? The second one in the basic series - Creating a Plugin - deals with a basic traits-based skill system, and introduces the concept of database fields and how to use them. The Replacing FS3 tutorial also has some tips for making your own skill system. If none of that helps, perhaps you could post some more specific questions in terms of what you’re trying to do and where you’re stuck?
Yeah, I’ve done that. I’m probably gonna do the plugin tutorial again and this time try playing around. I think the issue is I’m trying to run before I can walk. I found a good Redis tutorial that helped quite a bit too. Thanks for the help!
You shouldn’t need much of a redis tutorial. Ares hides redis away behind a database abstraction layer, so you never interact with redis directly. The Ohm database layer tutorials might help once you get past the Ares intros.
The main stumbling block with the few folks I’ve talked to seems to be that they want to jump right from “okay I did the intro tutorials” to “let’s code a super-complex skill system!”
While that’s an admirable goal, it is - as you said - a bit like trying to run before you can walk. The temptation to dive into the deep-end is strong because Ares already provides most of the minor utilities that most MUSHcoders cut their teeth on (multi-descers, who systems, etc.) But skills systems are very involved beasts.
I would encourage folks to start out with smaller chunks. For example, instead of trying to bite off “skills system” as a whole, tackle some of the simpler pieces first:
- A command to list what abilities are available.
- A command just to set an ability. No points, no error checks - those can come later. To start with, just store the value.
- A command to do the simplest possible die roll. Again, no fancy modifiers or changing the ruling attribute, or opposed rolls - just start small.
By starting small and adding pieces on, you can develop your skill system incrementally and it won’t be so overwhelming.
It’ll also be easier to get help, because questions like “I can’t figure out how to display my ability list” is way easier to tackle than “I want to code WoD for Ares but where do I even start.”
Thanks for the suggestions! I think I’ll do exactly as you say. My problem is Ares has me so excited I keep wanting to jump right into the deep end. Gotta learn to wade in the shallows first.
Thanks for the tips!
1 Like