• NOW LIVE! Into the Woods--new character species, eerie monsters, and haunting villains to populate the woodlands of your D&D games.

O.G.R.E. is here!


log in or register to remove this ad

Starting to play around with it. It's pretty neat!

There's no way to make easy if-then statements, right? Like, if I pop up a Male Dwarf, to roll on Male Dwarf Names table to get the right name? I imagine you can work this into cascading tables pretty OK, but a quick way to do that might be useful.
 

Starting to play around with it. It's pretty neat!

There's no way to make easy if-then statements, right? Like, if I pop up a Male Dwarf, to roll on Male Dwarf Names table to get the right name? I imagine you can work this into cascading tables pretty OK, but a quick way to do that might be useful.

That's part of the advanced scripting we're working on right now - IF/THEN, loops, switches, variables, etc.
 


Crazy awesome. :) Hahaha, EnWorld's very own remedial programming language! W00T!

You're actually missing some of the power of the setup in that you're duplicating tables I've already made rather than just hooking into them. Male/female and names being the standout examples - where you have two names, a 2-second change could give you thousands of names just by hooking into my name tables.
 

You're actually missing some of the power of the setup in that you're duplicating tables I've already made rather than just hooking into them. Male/female and names being the standout examples - where you have two names, a 2-second change could give you thousands of names just by hooking into my name tables.

yup. Think of it as division of labor. Morrus setup the gender and name table. Consume his table, rather than making your own as you make a new generator/table that uses his and adds other random attributes like hair color.

Share your tables. Borrow other people's tables. Good times.
 

I'm loving the generator, but I'm having another problem.

Twice now, when editing my Harmless Magical Mishaps table, I've tried to save the edits only for a "database error" to occur and I lose all my progress. It's especially annoying because incremental progress is hard to save, since the system won't save a table that isn't complete and parsable.

I'm not complaining, thank you guys so much for doing this! But is there any way you can figure out what the issue might be? I'm afraid to do any more fiddling with the system, for fear that I'll sink another half hour down the database error drain. :.-(
 

I'm loving the generator, but I'm having another problem.

Twice now, when editing my Harmless Magical Mishaps table, I've tried to save the edits only for a "database error" to occur and I lose all my progress. It's especially annoying because incremental progress is hard to save, since the system won't save a table that isn't complete and parsable.

I'm not complaining, thank you guys so much for doing this! But is there any way you can figure out what the issue might be? I'm afraid to do any more fiddling with the system, for fear that I'll sink another half hour down the database error drain. :.-(

Apostrophes. It's a bug we're aware of. When editing (not initially creating) a table, apostrophes cause a database error.

For the moment, the workaround is to avoid them! But we'll have that fixed very soon as I agree it's frustrating.
 

Oh man, thank you! I can work around them for now, just knowing the issue is enough to get me started, and again I really am grateful to you guys putting in the work on this project.

I tried debugging punctuation, looked at ? and ! and so on, but for some reason apostrophes didn't occur to me.

Thanks for the rapid response! If only other IT support was that prompt and helpful. :)

EDIT: At the very least, this re-taught me the good darn sense to save early and often.
 
Last edited:

Apostrophes. It's a bug we're aware of. When editing (not initially creating) a table, apostrophes cause a database error.

For the moment, the workaround is to avoid them! But we'll have that fixed very soon as I agree it's frustrating.

ah yes, the dread apostrophe (or Single Quote). That's actually a risk for SQL Injection attacks, and should be addressed ASAP.

EVERY field coming in from the screen that is incorporated into an SQL query should be run through a function to safety pad the value before it is concatenated to the query. I cannot stress that enough.

forex:
$val = $POST["txtName"];
$sql = "select * from Names where Name like '" + $val + ';"

this means that I can type "';drop database YourDB; select '" into the txtName text box on the screen and get it to run my bit of SQL to drop your database, or something else.

I'd have to look up the best recommendation for PHP, in general it's using a function like quotesmart() or just replacing all single quotes with a pair of single quotes.

$val = quotesmart($FORM["txtName"]);

To slobster, you can work around this bug by using a pair of single quotes:
Janx's Great Spell -> Janx''s Great Spell

When SQL sees a pair of single quotes, it realizes you mean to use a singlequote as content, and not signal the end of the single-quoted value.
 
Last edited:

Into the Woods

Remove ads

Top