AzureDVBB

# source: https://www.reddit.com/r/dungeondraft/comments/gjvlud/python_script_to_unpack_dungeondraft_pack_assets/

# dungeondraft_pack-unpacker.py
# version 0.1
# Based upon: https://github.com/tehskai/godot-unpacker

import sys
import os
import pathlib
import mmap

AzureDVBB

Keybase proof

I hereby claim:

• I am azuredvbb on github.
• I am azuredvbb (https://keybase.io/azuredvbb) on keybase.
• I have a public key ASD-rJGkdqK5mrkaALmXe5AFWsqfBPMZhPzKYbPqGJ9kggo

To claim this, I am signing this object:

AzureDVBB

// !!!! the following code is for the ATMEL ATTINY44 microcontroller !!!!
// display shift register pins
// positive edge driven
#define disp_clk        10// SRCLK to clock serial data into the shift register
#define disp_ser_latch  9 // latch pin to push changes in shift register and decoder to output
                          // the RCLK is directly connected while the LT is fed through an inverter
#define disp_ser        8 // SER (serial data) pin for theshift register

// pins for interrupt on button presses
#define button1         0 // Button for team 1 

AzureDVBB

# -*- coding: utf-8 -*-

# look into 'streamz' package, neat pipelining with dask integration
import cv2 # opencv-python for frame reading
import skimage # scikit-image for loaded image analysis
import dask # parallelized python EZ mode
import numpy as np # yep
import matplotlib.pyplot as plt # pretty charts no?
import matplotlib
from skimage.feature import match_descriptors, ORB

AzureDVBB

AzureDVBB

#include <PinChangeInterrupt.h>
#include <PinChangeInterruptBoards.h>
#include <PinChangeInterruptPins.h>
#include <PinChangeInterruptSettings.h>

/* FOR THE LOVE OF ALL MIGHTY PLEASE USE 1MHz CLOCK!!!!!!
 *  STAY AWAY FROM THE 8MHz INTERNAL CLOCK LIKE THE PLAGUE!!!!!
 *  I MEAN IT!!! THE MILLIS FUNCTION JUST DOES NOT WORK WELL!!!!!
 *  IT IS NOT FASTER BUT SLOWER FOR SOME REASON AND NOT ACCURATE!!!!
 *  SO PLEASE!!!! I BEG OF YOU!!! STAY WITH 1MHz INTERNAL CLOCK!!!!

AzureDVBB

# the little less documented way of adding a custom node tree
#   and populate it with nodes of varying types of I/O
#   sockets that work together, discombobulated

# first we import the blender API
import bpy


# then we create the UI space, the node tree as it is called
#   but in actualy fact this is similar to a UI panel/menu

AzureDVBB

#import the bpy module to access blender API
import bpy

#WARNING: this is written and tested for blender 2.79
#blender 2.8 and newer will likely have a different python API

#create a property group, this is REALLY needed so that operators
#AND the UI can access, display and expose it to the user to change
#in here we will have all properties(variables) that is neccessary
class CustomPropertyGroup(bpy.types.PropertyGroup):