-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathNOTICE
More file actions
103 lines (86 loc) · 5.09 KB
/
NOTICE
File metadata and controls
103 lines (86 loc) · 5.09 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
StarStats — Third-Party Acknowledgements
========================================
StarStats is licensed under the Mozilla Public License 2.0 (see LICENSE).
This file lists third-party works whose ideas, formats, or reverse-
engineering effort informed StarStats' implementation. None of the
projects below ship code inside this repository — only knowledge they
helped surface.
If you maintain one of these projects and would like the attribution
amended, removed, or expanded, open an issue and we will adjust.
----------------------------------------------------------------------
StarCitiSync (https://github.com/JiyanDev/StarCitiSyncPublic)
License: MIT
The v0.2.0-alpha additions to `crates/starstats-core/src/parser.rs`
recognise additional Star Citizen `Game.log` patterns — mission
lifecycle markers (`<CLocalMissionPhaseMarker::CreateMarker>`,
`CreateMissionObjectiveMarker`, `<EndMission>`), shop and commodity
transactions (`SendShopBuyRequest`, `ShopFlowResponse`,
`SendCommodityBuyRequest`, `SendCommoditySellRequest`), and clean
session-end signals (`<SystemQuit>`, `CCIGBroker::FastShutdown`).
The catalogue of which log tokens carry which meaning was informed by
StarCitiSync's open-source backend. StarStats does not copy code from
StarCitiSync; the regexes, dispatch shape, and tests in this repo
were written from scratch in Rust against synthetic fixtures. The
attribution exists because the *vocabulary* of what to look for —
which engine calls correspond to "mission accepted" vs "shop
purchase confirmed" — would have taken substantially longer to
derive without StarCitiSync's prior reverse-engineering work being
visible in public.
StarStats deliberately omits StarCitiSync's screen-capture / OCR-based
features. Anything that intercepts the running game process or its
rendered frames is outside StarStats' EAC-safe scope (see README:
"What StarStats does NOT do").
----------------------------------------------------------------------
Star Citizen Wiki / StarCitizenTools community
(https://starcitizen.tools, API: https://api.star-citizen.wiki,
source: https://github.com/StarCitizenTools)
Wiki content © Star Citizen Wiki contributors. Licensed under the
Creative Commons Attribution-ShareAlike 4.0 International License
(CC BY-SA 4.0): https://creativecommons.org/licenses/by-sa/4.0/
StarStats relies on the community-run Star Citizen Wiki API to
translate the internal class names that appear in `Game.log`
(e.g. `AEGS_Avenger_Stalker`, `KLWE_LaserRepeater_S2`) into
human-readable display names ("Aegis Avenger Stalker", "Klaus & Werner
Laser Repeater S2"). Without that catalogue every event in the
dashboard would surface as an opaque engine symbol; with it, the
timeline reads like a logbook.
The reference catalogue is fetched server-side, once per day, with no
user data attached to the request (generic `User-Agent` only — see
the privacy policy §3 for the full disclosure). The cached data is
keyed by class name and is never linked to any user account.
Modifications StarStats applies to the upstream dataset before
redistributing it (CC BY-SA 4.0 §3(a)(1)(B) "indicate if modified"):
* Internal Wiki bookkeeping fields (`id`, `created_at`,
`updated_at`, `version`) are stripped before storage.
* Per-category extras are lifted into a single JSONB `metadata`
column so the StarStats schema is uniform across vehicles,
weapons, items, and locations.
* Each entry is joined to the engine class identifier that appears
in `Game.log`, so the catalogue can be looked up by class name
rather than wiki page title.
* Entries without a usable class identifier are dropped because
they cannot link back to a game event.
* Where StarStats redistributes the resulting catalogue to users
(the public `/v1/reference/*` API and the `/kb` Knowledge Base
pages on the web app), the redistributed portion is offered
under the same CC BY-SA 4.0 terms — Attribution + ShareAlike.
No-warranty notice (CC BY-SA 4.0 §5): the wiki dataset is provided
by upstream "as is" without warranties of any kind. StarStats passes
it through without warranties of accuracy, completeness, fitness for
purpose, or non-infringement; the in-game live data may diverge from
the wiki at any time.
Attribution / link back. The "URI to the Licensed Material" required
by CC BY-SA 4.0 §3(a)(1)(A)(v) is satisfied at multiple levels:
top-level credit + link to https://starcitizen.tools in the web app
footer (every signed-in surface) and the /about page, and per-entry
"View on Star Citizen Wiki" deep links on every KB entity detail
page at `/kb/{category}/{slug}`.
StarStats is not affiliated with the StarCitizenTools team or the
Star Citizen Wiki. The wiki itself is a community project — entirely
separate from Cloud Imperium Games and Roberts Space Industries — and
the credit here is for the volunteer effort that produced and
maintains the underlying data. If a maintainer of the wiki or its
API would like this attribution amended, expanded, or the integration
adjusted (rate-limit headroom, caching shape, deep-link convention),
open an issue on the StarStats repository and we will discuss before
the next release.