Today I finished testing the fixes for initiative mode (known in game as ‘combat mode’ right now). I want to get a new update out very soon so we can get these fixes in your hands.
I then fixed a few UI issues that were arising when additional GMs were joining the board during a battle. One was simply the new GM’s UI was in the wrong mode. Another was that, upon entering battle mode they were immediately kicked to the UI for editing the lineup.. this was confusing more than anything else.
We’ve also had another little planning meeting and I’m hoping we can give you lots of reasons to be checking these updates over the next month a bit leading up to the kickstarter :)
Back tomorrow with more bits and bobs.
This dev log can also be found at https://bouncyrock.com/news/articles/talespire-dev-log-75
It’s late but I don’t want to skip this today so here we go.
Today I’ve mainly been focusing on bugs relating to the order of creatures in the battle-mode (also called initiative-mode) lineup. One such issue can be found here.
The main one from today was fixing the behavior when the currently active creature is deleted as control passed not being passed to the next in the list. I fixed that but I have seen a number of issues and I’ll need to test those pretty thoroughly before I’m happy to push this out. This code feels like a place where it is very easy to introduce regressions.
I’m hoping I’ll get the majority of the related issues cleaned up on Monday so we can push another update asap.
We actually have a bunch of asset changes too so we’d like to get those out soon too. These changes flesh out the various asset collections to match the tiles available in the test tile set.
Time to sleep, gotta get up early to watch the SpaceX RD1 launch tomorrow morning :)
Allo again, back with more of today’s messing around.
In the morning as planned I fixed the case where the Attack prompt remains if figurine is removed before confirming request . During the testing I found that there was a case where you could get the following.
- Gm0, Gm1 and Player0 join
- Gm0 adds Creature0 & Creature1
- Player0 tries to attack Creature1 with Creature0 and the UI appears to indicate that the attack is waiting on approval
- On Gm0 & Gm1’s clients the UI appears to approve of decline the attack
- Gm0 approves the attack
- The UI disappears on Gm0 & Player0’s clients
- The UI is erroneously still visible on GM1’s client
This was relatively easy to fix but testing took a while as after each attempt the build has to be copied to a couple of machines to test all 3 connections.
After that I added some platform specific code for controlling the hardware cursor so we can start tackling this issue.
Okidokey that’s all for today. Tomorrow I start with a bug where deleting a creature can cause subtle issues with the turn based line-up ui and.. well then I’ll grab another from the pile.
A quick sunday update for you.
Today I’ve been looking at this issue and looking into how best to tackle it. I’ve come up with a fix I’ll be coding and testing tomorrow morning but the issue was interesting as it gave me a change to look at the GM Request code with fresh eyes. Once again I’m seeing places where an effort to keep things extensible for an uncertain future has really just led to a more complicated system than neccessary (or rather one that has needed patching to line up with the actual behaviour we wanted later). I’ll definitely be looking at making this dumber in future.
This post is super vague :D but explaining the details (in this case) doesnt bring with it any cool takeaways.
Progress has been unexciting but continuous. I’ve pushed the changes that reveal corners of boards correctly in player mode. It does reveal a little too much but this will be fixed in future when the resolution of the ‘fog of war’ datastructure is increased.
Today I added the class for prop assets and refactored the building/serializing/etc code to handle this new asset kind. This being seperate now lets us at unique logic for these assets. We have experimented with having props temporarily ‘dodge’ out of the way of creatures and also be able to be places and rotated with more fine grain control than of tiles. Those experiments can now we ironed out and made part of the shipping game!
@Ree, whilst ill, has put a bunch of time into the changes we need to be able to more reliably get the invite emails passed filters. More on this soon.
I’m not going to be around on friday but will be working on Sunday instead so hopefully I’ll have another post for you then.
I’ve been messing around with fog of war and whilst it’s not there yet there has been progress.
The task right now if fixing this issue. The short version of the problem is that we have a data-structure that describes where has be uncovered (we call this a creature’s ‘memory’) and we have to sample it to see if a tile is visible. We can’t just sample in the center as maybe a tile is multiple units wide and only the corner has been revealed. We also can’t just sample at the center of each sub-tile as we get situations like this
|| || ____|| _____ __A__||__B__|
A is a wall and floor tile and
B is just a floor tile. If
B has been revealed then we have to see the wall (otherwise users get confused as to if it’s the end of the board or if it’s a hidden tile). This means sampling slightly outside of the bounding box of the tile. However this still can cause issues, such as the one linked above.
I played around with a few more schemes but today swapped it out with a mechanism that does a breadth first search of all the nodes within a bounds in the creature’s ‘memory’. This has a more expensive worst case than the other approaches, but the tests were seeming to show that to take enough samples for a good result we would be paying a pretty high cost anyway. The creature memory is stored in a quadtree so in many cases the search can succeed early as we don’t have to search the full depth to find a populated cell.
I haven’t got anything more today so I’ll bail now and give ya more news soon.
It’s that time again, today was spent:
- Finishing off the fix for If GM permissions are rescinded while any GM-only UI is visible, they stay on-screen
- Case where game spuriously entered cutscene mode when GM rights were removed from a player
- Initiative mode wasn’t updating the edit UI for remote GMs when local GM changed the line-up
- Reordering of lineup was not handled correctly in the edit UI
Clearmethod which was causing order issues when new elements were added.
Tomorrow I think I’m going to look at that fog of war issue causing corners not to appear. The first part is visualizing the points that are sampled for fog of war info and then we’ll see where the bug takes us.
Today I fixed the issue that all GM shared one flashlight. I also started looking into this issue where removing GM permission from a player doesn’t close some of the GM UI they have open. I think I’m on the right track with that one so hopefully I’ll have that one done in the first few hours tomorrow.
Alright that’s the most interesting stuff.
Yesterday we pushed out a little update. It was significant for us as it’s the first update after upgrading the version of Unity we were using. That’s always tense as it can be hard to ensure that everything is still working the way it was before. The update also included a proper fix for the bug from log 61 along with a few new nice to haves like shortcuts for camera rotation etc.
That bug fix was going to go out last friday but when we tested the release we saw that synchronization was broken between the clients for this like doors, chests etc. That was super weird and after a LOT of head scratching we found out that it was due to not having reprocessed a bunch of assets after the Unity upgrade. That was a bummer that we lost a day or two to it but good as rereading all the code helped me find and fix another unrelated issue.
Today I’ve mostly been looking at tickets reported by the community. We’ve not done a great job getting back to the awesome people who have filed tickets and that bums me out. Even though most get seen as they arrive the very least we should be doing is letting you know whether we can reproduce the issue. I’m gonna try to make sure I leave some time every day for that so I don’t fall behind again.
Once again thankyou all so much for the super thorough reports that have been coming in, they truly are invaluable.
Now that the last big tickets are dealt with I have a small gap before the UI for the new features is ready so I will get back on tickets again. Expect movement on those real soon!
Time for some sleep.
Heya folks. A quick one today. With both some life business and serialization fixes out of the way it is finally time to get back to tickets. People have been amazing at filing them so the fact I haven’t been triaging these for a week sucks. I’m gonna get through reproducing as many as I can today so I can then focus on fixing next week.
@Dwarf has been killing it making tonnes of progress updating all of the tiles to the new sizes and fleshing out the sets to include everything in the test tile set we made available in the last update. These will all count as new sets as, because of dimensions changes we can’t just swap then out with the originals without breaking your existing boards. Of course that will be coming with the floor changes but until then we want to keep everything working.
@Ree has made a pile of progress on props. As they will become their own class of object they can now have their own behaviors. This includes being able to be placed in way more place, orienting to the surface they are placed on and automatically ‘dodging’ out of creatures way if the creature steps in the same tile as some props. He’s also started on the floor UI as by nailing that we can then start on the deeper engine changes.
All go but mostly behind the scenes. We can’t wait to show you more though so thanks for joining us on this journey.
p.s One thing we haven’t made time for yet is tweaking the emails so they are less likely to end up in spam. We will be doing this for the next invite push though. When we do that we will re-email all codes to all of you who are already meant to have access.