Sept 6, 2018 3:09:17 GMT Benetnasch said:

Sept 5, 2018 20:11:30 GMT Gonzo said:

old school smt / persona. no "secret world" because that's too complicated. bunch of high schoolers (or whoever) living their normal lives until: boom, demons show up and they either have to use their personas, demons (via comp?), or guardian spirits (from smt if, i think—) to battle back.

please, i'm soooo in the mood for this after starting up persona 1 again

Gimme Soul Hackers or Devil Survivor I really liked not having to play a teen in Eternal Punishment, tbh. I can work with college students, tho.

I'm, like, not even halfway through, but I'm really loving Strange Journey and was already thinking that RPing out something like that plot would be really neat. 8O Instead of playing high schoolers, everyone on site is, like, a trained professional. Slightly more prepared for handling the apocalypse. Just. Just slightly.

I would also die for Devil Survivor, though, but that's probably just because I haven't actually played that many SMT games and that's the one in the series I'm the most familiar with, sdkjflhdkjfhsd.

Either way!!!! If y'all do this!!!! Hit me the heck up!!!!!!!

Honestly, hit me the heck up with any Persona sites with secret worlds, too, just. Hit me up with anything remotely (and non-canon, preferably) SMT related. If I can find time, I shall provide obnoxiously aesthetic skins. o>

There's a Big Bang project I just found out about that I really want to try, and sign ups are this month, but it's in a fandom I'm both new to and unfamiliar with, and I have ZERO idea what I would do for a story, send halp.

Why...................

I can't believe you've done this.

Sept 3, 2018 17:10:19 GMT Mouse said:

Whenever I'm looking for a posting template I always go through all of Pharaoh Leap's templates before going through anyone else's. No idea why.

Because you have bad taste. *sweats*

Nope~! The only difference is that, instead of writing it like

[attr="class","... you write it like normal CSS. But you probably had that figured out yourself. ;o

It's no trouble at all, though~! <3 Lemme know if there was anything yet that you had questions about!

We went out to a fancy restaurant, and all four of us kids got heckin' crab alfredo pasta, but none of us FINISHED our crab alfredo pasta, so my next seven meals are almost certainly going to consist of everyone's leftovers.

I had an amazing time, getting to see my mom and siblings for the first time all summer today, but now that I'm back to being home alone, all of the physical and emotional exhaustion from over this week has caught up to me. TuT

On the plus side, we went to a candy store, so even if I'm dead inside, I can drown my sorrows in sugar.

That's entirely up to you! There are some pros and cons.

I mostly put the CSS directly into the skin because it made styling it a lot easier with the visual editor (since I write up HTML in its entirety first, and then write up CSS afterward), but more importantly, it cuts down on a LOT of space in the code that people need to copy, paste, and edit. My thought process was that, the less bulky code there was in the template, the less likely less code literate members would get lost trying to find where they needed to edit things.

On the flip side, I've been told by people with slower Internet that CSS loading from the skin is slower than CSS loading from the template. This isn't really a problem if it's just the app in its app thread, but it can bog down loading times if you're looking at, like, the recent posts page and there are ten separate apps there.

I'd say code clarity takes priority over loading time in this case, mostly because it's not an issue on the page where it most counts (the app thread itself). For stuff like a member directory with individual members posts, though, it's better to put the CSS directly into the template, otherwise you'll end up leaving your slower-Internet-having members to DIE.

What you can do with CSS is definite a class – and then redefine that class when it appears within another class. How this is usually done in apps is that you specify the name will show up as yellow normally, but when that name is inside the class GROUPNAME, it'll show up as red, instead. This “overwrite” only works on the attributes you specify in the “overwrite”, so doing something like:

.class { height:20px;width:20px;background-color:red; }
.GROUPNAME .class { background-color:blue; }

will only change the background color, while leaving the other attributes as they're specified in the default .class styling.

That's the jist of it, anyway! Basically, by surrounding the whole app template in a GROUPNAME class, you can call on any class in the template and have it change depending on the name of that outside div. You could technically also surround each individual div you want to change with the GROUPNAME class'd div to get the same effect, but that's super tedious for both the coder and the app writer, so just... don't... do that.

Depending on the number of member groups you have on site, it may be easier to just set up pastebins with the GROUPNAME class already written in, but if you have, like, four or more member groups, it's probably easier just to direct people to where to change it, since it's really only finding and changing one word to one different word. You can make it easy to spot by having the very first line of code in the app be the div you change the name of, and only that div. Just remember that the name is going to be case-sensitive, so make sure people to know to change it to the proper casing.

Hopefully this answers your questions? ;u;

I would not wish this day on anyone aside from talking with guys in the voice chat, that was fun. I mean, I didn't get to play Persona 5 even a little! Tragic.