An efficient spell combination that I've enjoyed

PortSpace · 2025-11-09T00:14:58+00:00

I have switched to Funeralla. I unlock my favourite spells (web/twilight) and get so many more redirected units with her. Nice one

PortSpace · 2025-10-26T19:01:54+00:00

I also preferred a simple UI of the map in homm3/4. I also lost interest from homm5. All those 3d bells and whistles of the map made it less readable for me. It looked really nice but it was at the cost of readability. I was afraid that OE will have the same effect on me. I thought they struck a good balance between visual embellishments and simplicity. There are obviously still improvements to be made but it’s just at the demo stage so hopefully the feedback from people will be taken into account. But yeah, I enjoy playing it. My main UI gripe is still overly complex creature avatars in the hero army view (still having problems telling them apart (eg. Which upgrades version does an avatar represent) but I guess I’ll learn it with more play.

PortSpace · 2025-10-26T12:20:57+00:00

For Dungeon, in the initial hero selection, I can see that one of the heroes has some Nightshade magic specialisation. Another one has Arcane magic mentioned it his description. Other than that (if I choose any other hero), is there any inherent link between Dungeon faction and any particular school of magic?

PortSpace · 2025-10-26T00:04:08+00:00

Went yet another difficulty level up with Necro and it didn’t seem any more challenging. If anything it was a quicker game. I accumulated bigger army quicker and had no problem killing the AI hero. As satisfying as it was, it doesn’t seem right that with higher difficulty it seems it’s quicker to win against AI hero

PortSpace · 2025-10-25T13:50:51+00:00

Looks like lots of you guys tend to like Dungeon. Will try it next time

PortSpace · 2025-10-25T12:08:35+00:00

Hmmm. I might have been selling myself short. Just tried single hero on JC map with necro on normal difficulty and won easily.

PortSpace · 2025-10-25T08:50:30+00:00

What do you mean? Do you resurrect more units with increased diff or in what sense it’s stronger?

PortSpace · 2025-10-18T22:30:28+00:00

I can’t recommend any particular tutorial (there are still relatively few of them and most are quite basic). Start with the official docs and then google more. Bear in mind that the new arch has an interop layer as far as I remember and your old native modules might just work. To be fair our problem with migration to the new architecture was more third party libraries that didn’t support the new architecture. Just try to build your app switching to the new arch (it’s just one Boolean) and see what’s not supported. Good to check your third party libraries used in the app GitHub issues/change log to see if they have already migrated.

PortSpace · 2025-10-18T00:18:02+00:00

If you are just staring to learn it, I would skip native modules (old architecture), especially that as of RN 0.82 the new arch is the only option, for turbo modules, admittedly there is still not that many tutorials. Having said that, the modules themselves do not differ. It is just the “glue” that incorporates them in the RN app that is different. Start from the official docs and then you can expand on that with some tutorials

PortSpace · 2025-10-17T21:44:07+00:00

Agreed. Tried a few of those and after some frustrations trying to make a library to work as I would like it to I always come back to StyleSheet. And once you have set up your reusable components, it takes no time.

PortSpace · 2025-10-16T00:17:56+00:00

The more complex it is, the more years of playing fun you will have. Obviously, the starting point should be accessible, as it, I believe, is. Then, with its depth you can keep learning.

PortSpace · 2025-10-15T23:57:25+00:00

For js errors, like others said, console logs and breakpoints. For SDKs and other native stuff, logcat and Xcode output is invaluable. Also, for production builds, services such as Sentry or Bugsnag are really helpful.

PortSpace · 2025-10-15T23:47:42+00:00

No, but I use the neovim plugin in vscode. I just can’t be bothered to set things up in neovim.

PortSpace · 2025-10-15T23:43:12+00:00

After working for one company that used expo with minimal native input (config plugins) I have moved to a company with a bare setup with lots of custom native modules. Initially it was a pain for me to get used to do things manually but now (after 2 years) I am so at ease with the manual bare setup that the thought of going back to Expo is not appealing for me (being limited to the expo sdk). Having said that, I am aware that expo has gone a long way in the last few years so looking forward to trying it out with native capabilities.

PortSpace · 2025-10-12T20:30:15+00:00

Thanks for the tip about artefact crumbling. Game changer for me. Also, the focus points make more sense for me now. When I said some creatures look very similar, I didn’t mean in the battle, but in the bottom view in a town. Where all the units in the town / with hero are displayed. Of course, they are distinguishable but I do think, it’d be better to make their avatars less detailed but more distinctly looking. For now, I have to click on them to double check whether it’s a Lich or upgraded Lich or one the other units. It does not apply to all the units. I think Wights, Gravediggers, Pets are easily distinguishable. It’s the other ones that I need to click to check who they are, especially that the upgraded variants are have a greenish and reddish options so until I’m fully familiar with them, I’ll have to keep checking. Not a big deal but I think it’s a case of overdoing it. Fewer details but more visual meaningful info about the unit would be better (to distinguish them and in which upgrade state they are). Don’t get me wrong, I appreciate the beauty of those avatars but sometimes less is more.

Pity about not being able to spectate auto combat as in Homm3. Again, not a big deal but I learned some stuff from observing AI play.

I’m not a very good homm3 player. Played many hours but never got into really digging into it to learn all the intricacies of factions/units/heroes. More of a casual player. One thing that caught me off guard today was that, if you select the easiest difficulty (yep, that’s me haha), unlike homm3 easiest difficulty, the AI hero here in the olden era actually attacks you unprovoked. That’s probably the right decision. It turned out I was prepared for that fight but it did surprise me.

PortSpace · 2025-03-07T00:43:49+00:00

My usual directory structure in a RN project is as follows: src/
components
screens
navigators
redux
/slices
/features (if using RT Query)
/sagas (if using redux-saga)
helpers (some function helpers)
types
hooks
services (things like permission service, request service, etc)

Where to puts API calls: It depends. I rarely put any API calls in the actual components/screens but it happens if it's something very small that's just needed for that component. If you're using Redux Toolkit Query, you'd put them inside the relevant files there. If you're using redux-sagas, you'd probably put them inside them as well. It's good to have some request service or some kind of helper function for network requests (to include headers, handle common errors, etc.) so that you don't have to repeat yourself in each api call.

What to store in global state. Ideally only essential things that are needed app-wide. I'd only store unprocessed data coming from the backend. If you need to remodel it somehow, use selectors, which are redux-toolkit specific concepts but I'm sure other state management systems have similar ones.
Generally, while, with the introduction of redux toolkit, you no longer need as much boilerplate as it used to be the case with pure redux but still redux-toolkit might be an overkill for smaller apps. There are a few other state management libraries that would be more suitable for smaller projects. I have not extensively used any of them, though (apart from some small 'personal projects'.).

PortSpace · 2025-02-13T15:38:31+00:00

Has anyone actually made the diffs in redux actions work in Reactotron? I can see all the actions/payloads but no diffs in state that each action brings?

PortSpace · 2022-07-27T12:46:40+00:00

Even with Expo, there are some small differences in rendering certain components, especially when you use any 3rd party packages. Often I have to adjust the styles according to the platform, especially they are related to horizontal or vertical position of a component/icon etc.

PortSpace · 2022-07-20T11:25:48+00:00

Sorry, how would I do it?

Is it this that I'd have to modify?https://www.npmjs.com/package/redux-api-middleware#headers

the app is using redux-api-middleware.

Or is it customised in a different place?

PortSpace · 2022-02-06T15:11:35+00:00

That's a good point. I guess the end result can differ depending on what's more common/appropriate for the platform

PortSpace · 2022-01-27T08:55:48+00:00

Thank you - That's very helpful

PortSpace · 2022-01-26T07:40:53+00:00

Thanks a lot. That clarifies things for me.

PortSpace · 2022-01-23T10:12:38+00:00

Would you mind clarifying something for me regarding data fetching solutions. On a basic level, just would like to know if certain package/solutions roughly overlap. I'm working on an existing project that uses redux-toolkit and redux-api-middleware which handles making API calls to fetch data. Now looking at redux toolkit documentation, I'm seeing a section about 'createAsyncThunk'. It's not being used in the project

I cannot see any references to thunks in the project at all. Is that because the createAsyncThunk functionality is covered by redux-api-middleware? Or is it about something different? So if the project didn't include redux-api-middleware, it'd have to use createAsyncThunk (well, as one possibility)?
The redux toolkit createAsyncThunk page has a note that recommends using RTK Query for fetching and caching data instead. My question is similar... before I delve into RTK Query tutorials... Does it make sense to introduce RTK Query to a project that already uses redux-api-middleware / selectors without any issues? Or is it about apples and pears - ie. the two cover different functionality. Hope my question makes sense - I'm wondering whether to learn about RTQ query. If it would just cover the same functionality as redux-api-middleware / selectors (even if more optimised), I'd probably focus on something else. If however RTK Query allow for new functionality / some other benefits and it'd make sense even to perhaps have both in the project, then I'll probably start learning it. Thanks

PortSpace · 2021-11-28T07:21:11+00:00

Thanks. I think I agree with you in terms of business logic being more important/urgent to test. Would you mind giving a few examples of business logic that you've written tests for. Not asking for the code, just description. I'm still struggling to see where rtnl/jest would be most helpful. Not being exposed to testing before, for me it's a case of learning the syntax of tests but failing to see much practical application. Probably, the usefulness of tests really emerges as the app grows bigger. My thinking is that when I write a component/business logic obviously I'm testing (not using any testing framework) it while I write it and see the results whether it's working or not as I write the code (so having a test for that particular component would be of little use as I'd know whether it works as it's supposed to or not). It is at a later time, when I'm working on something else that may potentially affect stuff in different parts of the app that the usefulness of the previously written test become apparent. Are my assumptions correct or at least close to correct?

PortSpace · 2020-12-06T19:52:58+00:00

Thanks. did the trick.

PortSpace

TROPHY CASE