Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
I really like your mods and this game. I installed a bunch of mods and I am getting crashes now. Likely, an error in installation (incompatibility, etc) or maybe the class issue showed up again somehow. I'd like to know, is there any resource I can look at to try to fault-find? Error logs? I'd like to at least try myself what causes my game to crash so I can fix up my mods
Thanks in advance
there is the error.log file in the game dir, but crashes will not always output the error, so I think it is simplier to try mods one by one.
Would be a very good idea putting your source code up on github.
Would you elaborate on why it would be a very good idea putting it up on github?
I was surprised you haven't given the comments and history of your mod. I for one would love to see the source on such a reputable site.
I think the real question is more "Why not put it on Github?".
Yes...
https://www.microsoft.com/en-us/wdsi/filesubmission
https://www.google.com/search?q=cities+skylines+virus+mod&rlz
as well by putting your source on github or another service with any licensing you like, you ensure that if someone steals your code that you have evidence to prove that they went against your ToS. Which can greatly help with enforcing a take-down notice or further legal action.
Which license would you suggest?
Are you planning to contribute?
The microsoft submission does not require source, they will analyse all the files contained within your false-positive submission. Once verified your mod/s will be removed from the suspicious list and marked as a false positive. Which is a great step, as windows defender blocks files first and asks questions later.
I like GNU public licensing but a lot of people use GPL and to a lesser extent MIT. There are many other licenses and it just depends what sort of permissions you want to grant if any from your code. Personally if I'm releasing something for free, I don't want someone to use it in a paid option.
Some general info on licensing: https://www.synopsys.com/blogs/software-security/5-types-of-software-licenses-you-need-to-understand/
If I am able to contribute anything I'd love to. SLRR is a childhood past time of mine. For anyone to be able to contribute directly to your github I believe you need to add permission for them or they can post comments; otherwise they can 'fork' your code onto their own github but still must follow any licensing agreement and you would be free to checkout their changes, even incorporate said changes into your main branch if you wanted to.