Dev Log Week 2024-32/33: Accommodating Requests

I was on vacation for the past two weeks, so there isn’t much to report. But I’d really hate to break my streak of missing at most one week, so here we go :slight_smile:

This isn’t a problem, really, because at the end of the day, I am self-employed, so there’s never a week with no work. Obviously, there were the time-critical bits that just have to happen…like paying invoices or salaries. But I also spent an hour or two accommodating a request from the players of the Earhart exclusive game world, who implemented a custom slot renting scheme and needed the respective payments to happen between airlines. The heavy-lifting was already done on their end…I just had to convert it into a (very hacky) query to make it happen in game. This week, I’ll likely spent a bit more time to make this query (and similar ones) slightly less hacky in the future.

This also serves as a reminder that while exclusive game worlds usually come with a pretty vanilla configuration similar to what you’d find in public instances, we try to accommodate requests for “special features” whenever we can. This is usually the case when

  1. the effort isn’t excessive
  2. no or only simple custom datasets are required and
  3. required changes do not conflict with regular configurations.

That last point only really matters when we do custom development (charged extra), which we have done before as well.

If you are interested in such possibilities, either for an existing or a potential new game world, please don’t hesitate to get in touch.

1 Like