The printouts from Code One Army 7 do not include the "hackable" icon - neither for troops of a hackable unit type (HI, TAG, REM), nor for Hackers.
Posted this in another forum in the CodeOne section but it looks like more action is happening here, so here are my current issues which remain as far as I can tell (I've also emailed CB directly) - sorry to spam it in multiple places if that's against the rules... I just don't know where this will get the most traction/response. This is for the online app https://infinitytheuniverse.com/army/codeone Some of these refer specifically to the pdf/print export of the app and others to the app overall 1) Regardless of whether or not the app is set to cm or inches, the weapon ranges in pdf/print export always show their range in cm (pdf/print) 2) the opposite problem holds with movement, which is that it always registers in inches in the pdf even when the the army builder is set to cm (pdf/print) 3) Pistols SHOULD be able to function both as BS and CC weapons, but the profile for the standard pistol’s BURST mode is missing in all instances where a figure carries a pistol (this is true not just in the pdf export but in the army builder app itself - it simply does not show the Burst Mode on pistols) (both pdf/print AND app) 4) Weapons like the Heavy Flamer list “CONTINOUS DAMAGE” in their Traits. This is a misspelling of “CONTINUOUS DAMAGE” (both pdf/print AND app) 5) Some unit stats are cut-off in the print/pdf export (pdf/print) 6) pdf/print export likewise does not show that units have CC weapons and/or pistols. This may not matter in all cases, since figures typically have these weapons by default, but in the case of other figures like the Infirmars of Saint Lazarus and Knights of Justice (carrying Monofilament and DA CC weapons respectively) the lack of a stat line showing who is carrying what in the printed sheet is a massive oversight and requires you to just remember who carries what un-listed weapon. (pdf/print) A saved PDF included here with my notation showing the issues.
Can we please have the formatting be fluid, not stuck to 16:9 format screens / resolutions? On a 21:9 screen the whole left side unit list is not moving itself to left border, it stays where it would have been on a 16:9 one. It's infuriating because then the Weapons Chart can't fint to the side of the other boxes.
And another one - when you click on the unit name in your selected troop list, the unit entry doesn't switch to that unit's entry, like it does in N3 Army. Very inconvenient.
Also, what the heck is going on with movement values? Corvus Belli, can you guys please get your shit together? What kind of an introductory product is this for new players? :|
Can you please calm down a bit? you are not only overtly aggressive, but what you say is uncalled for. Find a bug? state were it is, what system, browser ectr and how to reproduce and move on.
Did you reloaded the page with CTRL+F5? Because some of these problem should have already been resolved (like the inches/cm thing)
What's uncalled for is three years of mucking around with the login system on the Forum. What's uncalled for is four months of Code One and basic functionalities being missing or broken on the C1 Army. Stats being a mangled mess as can be seen above. Asking the company to "get its shit together" is not "uncalled for", especially when you've paid top money for Op Kaldstrom with the intention to use it as advertised, as Code1 starter, and now you can't play it properly three months after release because the official army builder is broken in a myriad ways that you detect within 10 minutes of interacting with it. Are there no Q&A tests done on this software? Is there no upkeep? Is anyone monitoring the software and the database that obviously returns corrupted values? Bugs reported in the first post of this thread, April 27th, are still not fixed! That Shang-Ji entry still has two pistols. Code One feels like it was abandoned right after release. People have been calm and reasonable in this thread for four months and it got us nowhere. I tried that, as well as new window and relogging multiple times at the time. It was pretty clearly a database problem. Didn't check it specifically now.
Your language and behavior is uncalled for, I am expecting a minimal civility in the forum towards everybody, including company and its employees. I can understand frustration, I do not accept such expression of it.
I expect minimal respect towards the customer base from the company and having us wait for basic fixes for months or years on end is not that. Spouting off disinformation (Tohaa vanishing in Moscow, Bolts vanishing by Bostria just now) and disregarding the reaction of the community and not even making an official statement about it until pressured on the Forum or somebody semi-related to the company goes and asks them in person (like IJW did with the Bolts) to fix the misinformation is not respectful either. When the company and its employees start respecting me as a customer, I will consider being cordial and respectfult towards them. At this point, I will praise where it's warranted (and I do not hesitate to), but I will also bash all the stupid bullshit that keeps occuring over and over again and really shouldn't for a company of this stature.
Is there any official response from CB regarding when they will fix all this? As of right now I still find the Army Builder for C1 essentially un-usable and I've continued to refine my hacked-together database in Google Docs instead. The builder is still listed as version 7.0.0, which seems to imply there have been no updates (?) - as a new player to the game it's a bit disheartening. I get that people are speculating that CB has its hands full with getting N4 going, and that the C1 builder will theoretically get fixed after that, but... 1) C1 has been in the wild for almost 5 months now. What is an acceptable timetable for basic fixes in functionality (like the lack of BS pistol profiles and the inches/cm issues with pdf export)? Shouldn't an existing product take priority over one still in development? 2) What gives us confidence that CB will circle back around to C1 after N4 comes out? I would sort of assume that if N4 is their priority now, it will continue to be their priority after release (especially if they have to quash bugs with the N4 side of the builder). 3) I can't imagine that the same people who are revising the N4 rules and getting ready for release are also responsible for the coding and database issues in the C1 Army builder, so I don't quite buy that N4 is somehow getting in the way of C1. These issues should really be a pretty easy fix if there's any will to do so. Considering I whipped up essentially an entire replacement database in a few hours for my own purposes, and they just need to change a few values on their end. At a certain point, it begins to feel like they are going out of their way to NOT fix it. Any chance someone can kick this up the chain at this point?
The next big update for the army builder is on the 25th when the first wave of N4 profiles are added to it.
Agent Dukash (Combined Army) is now, according to N4, a Shasvastii - but the Code One profile has not been updated to accommodate this.
It might be a bug that the Charontid with +1 lieutenant order only has a standard sepsitor instead of a sepsitor plus, like the other Charontid options.
Army: O-12 Troop: Razor Browser used & Operative System: Browser & App Description of the bug: I'd assume the Razor unit's Infiltration skill is not shown in the profile.
C1 Alguaciles Lt are listed as 1 SWC on the Army, and 0 on the datacards. I think the datacards are right, because otherwise the SWC cap would be exceeded at 15 pts
I spotted some irregularities when looking through the Combined Army listings Effectively rules or terms that apply to N4 but not to CodeOne: 1) FTO options on M-Drones and T-Drones. There are no Fireteam rules in CodeOne so having things listed as “Fireteam Options” seems unusual. The term FTO doesn’t seem to appear anywhere in the Wiki or even in the Fireteam Rules Annex. If you’re going to use an acronym it’s best practise to define it somewhere in your documentation, particularly if it’s a rarely used acronym. 2) The Sphinx has Remote Presence in CodeOne. Infinity Wiki says “This N4 rule is not used in CodeOne.” I think that’s all for now. Thanks!
