![]() This is required functionality in order to get any joy from playing a military mod like explained here: Ĭ - Official Public Servers: Improve the multiplayer mode with official public servers (this includes time limits, password protection of players, automatic restart when the game ends etc).ĭ - Better Graphics: Improve the graphics - both the User Interface (for example a skin for the colony panel) and the terrain (nicer transitions, better hills/mountains, animated fish jumping out of the water etc).ĪBCD - All of the above: Try to do a bit of everything.Īhh yes your thoughts reminds me of an old thread I made on the FreeCol sourceforge forum a few years back. If you're not on discord then I've setup some reddit vote fields below!Ī - AI Colony Management: Make the AI manage the colonies well (making specialized colonies, utilizing experts properly, making the correct tile improvements and the correct buildings).ī - AI Military: An AI using a tactical map for placing the soldiers where there's an actual threat (would also be used for making unarmed colonist avoid dangerous areas, and for planning assaults on enemy settlements). I've jumped back to Android Studio Arctic Fox (2020.3.1 Patch 4) for the moment, however this brings with it other issues (my current core project targets the latest SDK version, which requires the updated IDE).Ībsolutely any help with this would be insanely appreciated.Stian has asked over on the Colonization fans discord in the FreeCol chat area what would fans like him to prioritize over the months to come in the lead up to the big FreeCol v1.0 release. It appears as though the moment Google Chrome shows the connected physical device in the chrome://inspect/#devices page, the physical device promptly becomes unavailable through Android Studio. However I've been unable to do anything with the above discovery, other than close Google Chrome, and hope for the best. Then I can connect with Android Studio and then restart Chrome and reconnect. If Chrome is connected using chrome://inspect, then adb seems to disconnect. After trying many other posted solutions, I discovered that the issue was with Chrome also trying to connect its debugger to a web view. I have been fighting for a few days with adb not seeing my device. This particular comment in one of the above issues clued me onto a possible root cause:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |