FAQ

Yes. Every completed commission includes 30 days of support for reasonable follow-up changes, small fixes, and adjustments related to the original work. If something feels off after delivery, I would rather help clean it up than leave you stuck with it.

The support period covers smaller tasks that naturally come up after a project is finished. That can include theme tweaks, addon configuration, fixing settings, user groups, forum nodes, minor layout issues, and similar cleanup work. Larger new features or changes outside the original commission may need to be treated as separate work.

Sorry, no. I keep commissions paid because this work helps me make ends meet, and I have to be careful with my time and energy. I appreciate people asking respectfully, but I cannot take unpaid trades, exposure deals, or favor exchanges.

For commissioned website work, I currently focus on XenForo-based websites and forums. That focus is specific to website commissions, not a statement about everything I do, so please do not assume all of my work is XenForo-only.

Generally, no, not right now. My commissioned website work is currently focused on XenForo, so other kinds of websites are usually outside what I take on. This is specific to websites — other kinds of commissions, such as software, automation, or tooling, are a separate matter and are not covered by this restriction.

No, not currently. Most of my XenForo work has been around the versions and workflows I know well. I prefer not to accept XenForo 2.X work unless I am confident I can deliver it properly.

Quite a bit. That includes installation and setup, configuration, user groups and permissions, forum nodes and node permissions, addons, themes and styling, DNS/Cloudflare setup, and custom tweaks or limited development where it makes sense. I will let you know upfront if something is outside what I can reasonably handle.

No. I do not work with Enjin sites. My experience and interest are focused elsewhere, so I would rather be honest up front than take on a platform I do not enjoy or specialize in.

PowerShell modules, Python scripts and CLI tools, C# applications, small utilities, workflow automation, file-management tooling, backup and media workflows, and integrations or glue-code that connects two things that should already talk to each other. I am generally interested in practical tools and automation that solve an actual problem rather than software for software's sake.

There is no hard language lock, but PowerShell, Python, and C# are the languages and stacks I work with most often, so that is where I am most comfortable. The problem and scope matter more than forcing everything into a specific language. If a project needs a stack I am not confident I can deliver properly, I will say so upfront.

Yes, potentially. Existing scripts and tools are fine to work on if the codebase is reasonably understandable and the requested work is within scope. I may decline badly broken, undocumented, or excessively large inherited projects if bringing them up to a workable state would take unreasonable effort.

Case-by-case. Small and medium utilities, internal tools, automation, and focused applications are a more natural fit for what I do. Very large software products or platforms are not something I automatically accept, so I would rather scope it honestly upfront than take on more than I can properly deliver.

Yes, the same way as any other commission. Completed software work includes the same 30-day support period, covering reasonable fixes, adjustments, and small follow-up changes related to the original work. Larger new features or expanded scope may need to be treated as separate work.