Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Readme isn't up to date #124

Open
Azurency opened this issue Sep 24, 2017 · 11 comments
Open

Readme isn't up to date #124

Azurency opened this issue Sep 24, 2017 · 11 comments

Comments

@Azurency
Copy link
Owner

Issue by JHCD
Friday Feb 24, 2017 at 08:55 GMT
Originally opened as CQUI-Org/cqui#327


NOTE: Until this mod is in a less experimental state, the mod will not remember its "enabled" status after restarting the game. This means that every time you plan to start a new game using CQUI, you'll need to explicitly enable it in the "Additional Content" menu first. Once you've created the game using the mod, it will always load when you start the save, regardless of its current status in the "Additional Content Menu"

Is this still up-to-date?
It's always enabled here.

@Azurency Azurency added this to the Beta Release milestone Sep 24, 2017
@Azurency
Copy link
Owner Author

Comment by chaorace
Friday Feb 24, 2017 at 08:58 GMT


No, it's no longer an up to date description. I plan to just completely rewrite the readme for the Beta release

@Azurency
Copy link
Owner Author

Comment by JHCD
Sunday May 21, 2017 at 07:12 GMT


We need a documentation of all used key bindings and mouse-click implementations too.
Has anybody an overview about the possible features?

See #536 and #529 for example...

@ricanuck
Copy link
Contributor

Not only the readme, we should also work on the Steam WS description and make it actual, especially now that the C stands for Community. I would also make every file name person-neutral, get rid of any names and personalization so that we truly reflect the Community nature of this new edition (in-code comments with names are OK, and even better, as they help identify code authors for better troubleshooting)...

I can help with the descriptions, if you want..

@sparrow8332
Copy link
Collaborator

@ricanuck any help is appreciated mate. @Azurency is on the ball with the updates and i would have started a fresh readme and clearing out the files ect but been bogged down so much recently with work.

@ricanuck
Copy link
Contributor

yeah, I know, work, that stupid invention that prevents us from civving freely... 🤣

@Azurency
Copy link
Owner Author

Why would we remove all the names and thanks ? I think it's good to thank the people who contributed, that the community ! Maybe just make it more compact on the readme

@sparrow8332
Copy link
Collaborator

or maybe even a link to a Pastebin with all the names off everyone thats helped get this to where it is Past & Present

@ricanuck
Copy link
Contributor

@Azurency : Antoine, I was referring to removing names from file names... right now there are some files with user names, I meant we should make all those file names neutral... off course contributor's names should stay! But the mod itself, and any of its parts, should really be person-neutral, now that the "C" stands for COMMUNITY and not for a person... capisce? 😉

@sparrow8332
Copy link
Collaborator

@ricanuck ive started on sparrow8332-patch-1 branch - CQUI.modinfo for eg is this what you mean ?

@ricanuck
Copy link
Contributor

ricanuck commented Oct 2, 2017

Yep, that is what I mean... neutral file names. That one should just be CQUI.modinfo...

@ricanuck
Copy link
Contributor

ricanuck commented Oct 2, 2017

Comments inside the code are OK, in fact it's better to know who wrote what for easier troubleshooting.

Azurency added a commit that referenced this issue Oct 22, 2017
- Updated the readme to make it more clear (see #124)
- The readme still need some more corrections and improvements
- Rolled back the shadow of the policy reminder popup
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants