Adding 'Code Editor 2' theme file and related install instructions to INSTALL.md

[OptimalNoob]

No description provided.

[coderabbitai]

📝 Walkthrough

"""

Walkthrough

A new Dracula color theme file for GameMaker has been introduced, providing detailed color and style definitions for various syntax scopes. Additionally, the installation documentation for all supported platforms has been updated to include instructions on installing this theme in the Code Editor 2 (Beta).

Changes

File(s)	Change Summary
Dracula.tmTheme	Added a new XML-based color theme file with detailed scope-based color and style settings.
INSTALL.md	Updated installation instructions to include steps for installing the Dracula theme in Code Editor 2 (Beta) on Windows, MacOS, and Linux.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant GameMaker Editor
    participant Preferences/Settings

    User->>GameMaker Editor: Open Code Editor 2 (Beta)
    User->>Preferences/Settings: Navigate to Preferences/Settings
    User->>Preferences/Settings: Select Theme option
    User->>Preferences/Settings: Choose "Create new theme from file"
    User->>Preferences/Settings: Select Dracula.tmTheme
    Preferences/Settings-->>GameMaker Editor: Apply Dracula color scheme
    GameMaker Editor-->>User: Display editor with Dracula theme

Loading

"""

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 99b4fe0 and cd1bd0a.

📒 Files selected for processing (1)

• Dracula.tmTheme (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• Dracula.tmTheme

✨ Finishing Touches

🧪 Generate Unit Tests

• Create PR with Unit Tests
• Post Copyable Unit Tests in Comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai auto-generate unit tests to generate unit tests for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 1

🧹 Nitpick comments (3)

Dracula.tmTheme (2)

1-1: Remove BOM from XML header
The leading invisible character before <?xml indicates a Byte Order Mark. Some plist parsers may fail on BOM-prefixed files. Please save without BOM to ensure compatibility.

---

128-136: Avoid duplicate entry name for placeholder escapes
You have two entries named “String Escape Characters” (scopes constant.character.escape and constant.other.placeholder). Consider renaming the second to something like “Placeholder Escape” to improve clarity.

INSTALL.md (1)

17-24: Unify heading casing and link formatting
The optional Code Editor 2 sections use inconsistent “Install instructions” casing across OS blocks and plain URLs. For consistency:

• Capitalize “Install Instructions” to match main headings.
• Use markdown link syntax (e.g., [master.zip](https://github.com/…)) for readability.

Also applies to: 40-47, 62-68

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 04d7722 and 99b4fe0.

📒 Files selected for processing (2)

• Dracula.tmTheme (1 hunks)
• INSTALL.md (3 hunks)

[OptimalNoob]

missed some bad pasted xml properties originally, removed those

[tonystr]

Looks good to me 👍