User talk:Hale's Own Troll

Welcome to D&D Wiki!

Behold! A Whole bunch of nothing, for the most part!

I attempt to play DnD, despite the fact our group hasn't met in about 2 months(Rip). Other than that I play dota 2 and the Commander varient of Magic.

As of right now, I only have one weapon to my name here: Entropy's Vessel, A cursed magic weapon that is just as likely to help you win a battle as it is to randomly blow you up, which is quite often. It has a high personal utilization of the Wild magic table, so even if you didn't handicap yourself by picking the more fun, but objectively worse, option; don't worry, as this weapon will have your back! Or your new Beard! Or just disintegrate it because you just so happened to roll a level 5 fireball with you at its center! The game will never be dull with your new friend around, unless your a fun burglar and decide to remove its curse by wishing it away or something.

gollark: XTMF was not really designed for this use case, so it'll be quite hacky. What you can do is leave a space at the start of the tape of a fixed size, and stick the metadata at the start of that fixed-size region; the main problem is that start/end locations are relative to the end of the metadata, not the start of the tape, so you'll have to recalculate the offsets each time the metadata changes size. Unfortunately, I just realized now that the size of the metadata can be affected by what the offset is.

gollark: The advantage of XTMF is that your tapes would be playable by any compliant program for playback, and your thing would be able to read tapes from another program.

gollark: Tape Shuffler would be okay with it, Tape Jockey doesn't have the same old-format parsing fallbacks and its JSON handling likely won't like trailing nuls, no idea what tako's program thinks.

gollark: Although I think some parsers might *technically* be okay with you reserving 8190 bytes for metadata but then ending it with a null byte early, and handle the offsets accordingly, I would not rely on it.

gollark: Probably. The main issue I can see is that you would have to rewrite the entire metadata block on changes, because start/end in XTMF are offsets from the metadata region's end.

This article is issued from Dandwiki. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.