Started by Deadcode, December 31, 2018, 12:10 AM
0 Members and 1 Guest are viewing this topic.
Quote from: Asbest on December 31, 2018, 10:44 PMI didn't read whole, but will be real time worms? like real time ttrr etc. If no, its very sad.
QuoteIt is now possible to start an offline game with CPU teams only, and no human teams present, pitting the CPU to play against itself.
QuoteIt is now possible for the host in an online game to add CPU teams. The game will only be allowed to start if all clients present support this feature.
QuoteAuto-place worms by ally (checkbox) – When worm placement is automatic, group worms by team colour. May make automatic placement feasible even in Fort-style maps. Default off.
Quote from: Deadcode on December 31, 2018, 12:10 AM(Endless list of bugfixes and features)
Quote from: Kradie on December 31, 2018, 12:41 PMYou have my gratitude! Thank you so much for your hard work CyberShadow & DeadCode! This will surely put smiles on many faces and continue to bring life to this legendary epic game! I am so proud of everyone
Quote from: Godmax on December 31, 2018, 11:02 AMOk so....it fixes non existing bugs (I have never encountered?!). How about a way to continue games after a disconnect how about that?
Quote from: TheKomodo on January 01, 2019, 12:24 AMWow that makes my longest post ever look like nothing But seriously, these are the new things i'm most excited about:QuoteIt is now possible to start an offline game with CPU teams only, and no human teams present, pitting the CPU to play against itself.QuoteIt is now possible for the host in an online game to add CPU teams. The game will only be allowed to start if all clients present support this feature.QuoteAuto-place worms by ally (checkbox) – When worm placement is automatic, group worms by team colour. May make automatic placement feasible even in Fort-style maps. Default off.I'm really interested to know more about auto-placement, we've been dying to have this in Darts for as long as we can remember, there are many people who don't like the scheme specifically because they must wait a while placing worms at the start, this changes everything there! Couldn't be happier!Great work on the bug fixes, I didn't realize the game had so many issues... Will be nice to try some of the other things too I hope i'm still alive for 4.0, not even joking!
Quote from: StepS on January 02, 2019, 10:19 AMAs a reminder for anyone who wants to have CPU-only games (with no human teams present), you can already do so by using this WormKit module. It allows the "start game" button to be pressed.You will have to delete the module when 3.8.0 is released.
Quote from: j0e on January 03, 2019, 01:34 AMThe best thing about WA is how polished and perfect it is, and that is something Team17 still fails to comprehend. There will never be a worms game that comes anywhere near WA in quality. This new update cements that fact indisputably.
Quote from: cuck on January 03, 2019, 03:35 PMHello,First, I think it's great that you're making things for W:A. But I'm afraid that many members of the community are somewhat disappointed by the changeset featured in the 3.8 update. Even though fixing bugs is important from developer's standpoint, it is not necessarily the best course of action to maintain a healthy community. From my understanding, the sole thing that people anticipated from this update was a set of new and meaningful gameplay features.From the quick glance of the changeset, most of the changes were directed towards fixing obvious bugs with windows 10 compatibility (yay!) and resolving glitches that were low level and so obscure, that we didn't know they even existed (yay... maybe?). Don't get me wrong, some technical features (ASLR) and fixes were truly necessary, but I bet that most players can live through a sea bubble skipping an animation frame.The thing that I cannot comprehend at the moment, is why do have to stick with absolutely perfect backwards compatibility across multiple WA versions. Most folks on WormNet stick with 3.7.2.1 (because it's newest* and greatest at the moment), 3.6.31.0 (because of ProjectX) or 3.7.2.2 (because they don't know any better and just use what steam installed by default). Yet, there has been substantial amount of work put into bringing back WA 1.0 to play nicely with 3.8. Too bad, that WA 1.0 is unobtainable at the moment, so the only somewhat viable way of playing 1.0 in the year 2019, was if someone's grandma found an ancient CD and wanted to relive the good ol' days of The Berlin Wall falling down. More of the time could be spent on more meaningful changes if we just decided to drop the compatibility support and print a nice prompt to update the game when somebody joined the party with their 1920 Ford model T. Btw, even if the core game can synchronize with 1.0, the Napoleonic Wars veteran will still be kicked out/desynchronized because he lacks the rubberworm or other modules.The power of WA is it's great community, that has already proven numerous times that it *can* and *will* bring many new exciting features through the Wormkit. Even better, we are backed by two truly skilled developers with access to the game's source code, so some technical and otherwise unfeasible changes can be done at the source code level. But I'm afraid this update missed the chance to revitalize the game. Of course, nobody expected a full ProjectX reimplementation, but at least a cornerstone of a true Wormkit system could be laid. We all know, that in its current state wormkit is a fancy name for LoadLibraryA wrapper and module developers are left to figure out everything by themselves. As result, every wormkit module implements important stuff in a chaotic way that often does not play out nice with other modules or game features. Of course, now* rubberworm is a part of the core game, so it is bound to behave nicely, but all other modules need to be redone or patched anyway with the same nonexistent API.The limitation of WA's feature development is the lack of public information (developers need to reverse engineer everything by themselves), lack of true integration between modules and the game, and the way the game's memory structures are laid out and referenced. Most of the game code and structures are easy to find and understand in a single evening's time with a 6 pack of beer. So for example, replacing bazooka's physics and behavior is relatively easy, but extending the weapon roster with that modified bazooka is a hell of a task. Why? Because there is no room. Hacking the game to think that the weapon roster contains 128 entries is easy, but when the game would check the ammunition of red team's weapon #128, it would actually check the blue team's weapon #48 or so. In order to truly add a new weapon to the game, the developer has to copy the entire weapon entry array and ammunition state array to a new area in memory, insert some buffer space between the array entries and force the game to use the new memory area with regards to extended intervals between entries - find and patch hundreds of references to the old memory address and inlined constants. Btw, even if the modder has achieved such task, there are still dozens of arrays and subroutines that need to be altered (loading custom sprites, img's, sounds and localization strings, extending the arrays containing the pointers to loaded data, modifying the weapon box to show more columns, etc.). Each task involves the same or greater amount of work and further changes to other parts of the game. On the other hand, the owner of the source code to do the same task only has to change some constants and recompile the game.Extending the game with bigger weapon roster (alongside more team, player, sprite and other miscellaneous arrays) will break backwards compatibility (even though some protocol messages actually offer more space than needed), but if we just prompt the outdated player to upgrade the game, we will be just fine.In regards to lack of documentation and integration between the game and modules, maintainers could develop a basic ProjectX-like environment (let's call it a True Wormkit), allowing for package management across players, dynamic hooking and unhooking api, game protocol access, easy access to game's memory structures, and reading/writing to new scheme format (I hope the new scheme format is a JSON or XML file, so modders can easily extend it to their own needs). And I strongly believe, that releasing (partial) header files of important structures and functions won't cause harm to anyone. With extended buffers and a proper modding API true miracles could be done.If the community has to make a leap to 3.8 and redevelop most of the modules, please at least make it worthwhile.
Quote from: cuck on January 03, 2019, 03:35 PM*wall of text*