Skip to content

Siv3D Game Jam 2023

BANDAI NAMCO Studios Cup | Siv3D Game Jam

Theme: "すくう"

Winning Works

1. Registration

(Registration has ended)

2. Event Schedule

For Zoom participation, displaying your real name and turning on your camera are not required.

2.1 Opening Ceremony October 21, 2023 (Sat) 14:00-14:30 (Zoom opens at 13:30)

  • Explanation of the event and announcement of the theme.

Opening Ceremony Slides Theme Announcement Slides

2.2 Midterm Presentation October 28, 2023 (Sat) 14:00-15:30 (Zoom opens at 13:30)

  • The moderator will share their screen to visit each team's work introduction page and provide comments or questions for about 1 minute. Team representatives should respond via microphone. No presentation preparation is required.
  • Please create a work introduction page on Scrapbox by the midterm presentation.

Midterm Presentation Slides

2.3 Work Presentation November 5, 2023 (Sun) 14:00-16:00 (Zoom opens at 13:30)

  • Team representatives will take turns sharing their screen and give a talk of up to 90 seconds about their team, work, and development. It would be good to prepare slides.
  • Since detailed information and gameplay videos can be viewed from the work introduction page, focus on conveying key points and appeal points. There will be no Q&A session.
  • Please complete your work introduction page on Scrapbox by the work presentation. Also, register your work using the Work Registration Form.
  • Even if incomplete, please present your progress so far and future prospects.

Work Introduction Page (Scrapbox)

General Announcement Slides

2.4 Comment Sheets & Prize Delivery

A judging session will be held in late November. After that, comment sheets and prizes will be sent to eligible recipients.

3. Rules

Anti-Harassment Policy

In organizing the BANDAI NAMCO Studios Cup Siv3D Game Jam, we have established an anti-harassment policy. To maintain a space where everyone can gather without conflict, we ask all participants to agree to the following policy and appreciate your cooperation. Harassment includes, but is not limited to, the following:

  • Offensive comments (regarding gender, gender identity or expression, sexual orientation, disability, appearance, body size, race, ethnicity, age, religion, etc.)
  • Threats, stalking, or following
  • Harassment-oriented photography or recording
  • Sustained disruption of presentations or events
  • Inappropriate disclosure of information including posting sexual images
  • Encouraging or defending any of the above behaviors
  • Other behaviors deemed as harassment by the organizers

During presentations and discussions, there may be situations where unconscious bias-based remarks are made without the speaker being aware of their inappropriateness. When communicating, please consider the other party's position and communicate with consideration for the healthy operation of the event. If you experience harassment or notice someone else being harassed, please contact the organizers immediately.

Work Development Rules

Submission of Previously Published Works is Prohibited

To ensure theme-based work development and allow participants to start from a similar starting line:

  • Works already presented at other events (contests, exhibitions, conferences, etc.) with 10 or more participants
  • Works already distributed on the web in a working state

Submission of works that fall under either of the above categories, or works that are merely arrangements of such works, is prohibited.

Main Program Must Be Developed Using Siv3D

  • The main program of the work must be developed using Siv3D.
  • Programs that assist game operation or are used during production are free to use other tools.
Rights to Deliverables

Rights to Deliverables Belong to Participants

  • Copyright of works belongs to each developer.
  • Information disclosed in midterm presentations and final presentations becomes "publicly disclosed," allowing third parties to quote within appropriate limits to express opinions and impressions.
  • When publishing work source code, you can choose an open source license (free to use if you follow the displayed license) or no license display (others cannot use).

However, Event Organizers Also Have Rights to Publish Work Information

  • Work screenshots, videos, descriptions, etc. may be posted by event organizers on web pages, promotional materials, etc.
Use of Third-Party Copyrighted Materials

Follow Licenses and Terms of Use for Third-Party Copyrighted Materials

  • Follow licenses and terms of use for programs, images, audio, video, and other materials used in works.
  • Organizers are not responsible for troubles arising from improper use.

For Materials Created Using Generative AI Tools, Follow Tool Terms of Use

  • For materials created using generative AI and other tools, follow the tool's terms of use.
  • Organizers are not responsible for troubles arising from improper use.

No License Handling Required for Official Siv3D Code

  • Siv3D and Siv3D's official tutorials and sample code are already licensed within Siv3D programs, so you can use and modify them without any additional steps.

4. Platforms for Participants

4.1 Information Hub Page

  • This page. You can check important matters related to the event.

4.2 Siv3D Discord Server and Event-Specific Channel #bnscup2023

  • You can exchange questions and opinions about the event, development, and Siv3D.
  • If you are already a member of the Siv3D Discord server and entered your Discord ID in the Connpass registration form, you have been invited to the #bnscup2023 channel.
  • If you wish to be invited to the #bnscup2023 channel later, please contact us individually following the procedures listed in the #general channel of the Siv3D Discord server.

4.3 Twitter 𝕏 Hashtag

5. Work Introduction Page (Scrapbox)

Work Introduction Page (Scrapbox)

  • Please receive editing permissions for the work introduction page through the #bnscup2023 channel on the Siv3D Discord server or via email sent from the Connpass system before the opening ceremony.
    • If you haven't received editing permissions by the opening ceremony, please contact us.
  • You can easily write images, videos (YouTube), code, URLs, etc., like in Google Docs to freely create your work introduction page.
  • You can also interact by writing questions and comments on other teams' work introduction pages.
  • Edit history is saved and regular backups are made.

6. Final Day Work Registration Form

Please cooperate by submitting by November 5 (Sun) 13:55.

7. Contact / Q & A

  • Contact with organizers and technical questions are handled on the Siv3D Discord server.
  • For privacy-related matters only, consultation via email (Siv3D representative Suzuki) reputeless@gmail.com or Discord DM is also possible.
About Team Participation

Q: When participating as a team, do all team members need to register individually on Connpass?

Registration is recommended. While it's possible not to register, it becomes inconvenient as you won't receive important notifications or evaluation comment sheets.

Some Team Members Cannot Attend Certain Events

Q: Some team members have difficulty attending the opening ceremony and midterm presentation. Is full team attendance required for the opening ceremony and midterm presentation?

For teams, one representative attending each of the opening ceremony, midterm presentation, and work presentation is sufficient. However, attending as much as possible will deepen understanding of the theme and event purpose. Please share information thoroughly among members.

Cannot Attend Midterm Presentation

Q: I have classes on the day of the midterm presentation and it's difficult to attend. Is this a problem?

If you don't present at the midterm presentation, feedback at the midterm point will be based only on your work introduction page. The midterm presentation is mainly for improving second-half work and exchanging opinions, so not participating will reduce the feedback you receive but won't directly affect final results like awards.

Receiving Event Notifications from BANDAI NAMCO Studios

Q: Despite selecting "Do not receive notifications" during registration, I'm receiving event information via Connpass.

Due to Connpass service specifications, when you participate in an event, you automatically join the event organizer's "group." After that, notifications may be sent when the event organizer creates new events on Connpass. To stop notifications, change the email notification settings for the Connpass "group" or leave the group. The "Do not receive notifications" survey item is different from Connpass notifications.

Changing 'Do Not Receive Notifications' Setting

Q: I answered about "employment-related notifications" in the registration survey, but I want to change my answer.

Since we removed the Connpass event participation deadline, you can temporarily cancel event participation and re-register with the same account to change survey answers without leaving a cancellation history on Connpass. Email addresses for prize delivery can be changed using the same method.

8. Development Resources

9. Executable File (Work) Submission Method

General information about creating executable files in Siv3D is explained in Zenn Siv3D Tutorial 41 | App Publishing . This section summarizes basic content for game jam participants.

9.1 Creating Executable Files

Each time you build Siv3D, an executable file (ProjectName.exe) is output to the App folder. If your program doesn't explicitly load external files (example/windmill.png, タイトル画像.png, MyBGM.mp3, etc.), submitting just that executable file alone will make your work run. If you're loading external files, you'll need to submit the executable file along with all those external files.

Siv3D's standard emoji, icons, and standard fonts (fonts without specified file paths) are automatically embedded in the executable file, so no file bundling is required. As an exception, on Windows, if you write GlobalAudio::BusSetPitchShiftFilter() in your code, please bundle the dll folder. Also, contents of the example folder are not embedded.

Executable files can be built in two ways: Debug build and Release build. Debug builds generate extra debugging information and slow code, which can reduce game frame rates. Be sure to submit executable files built with Release build. Debug build programs display Debug Build in the window title.

9.2 External File Placement

If your program loads external files, place files at positions relative to the executable file and bundle them. Here's an example of the final submission directory structure when the executable file is game.exe.

Example 1

void Main()
{
	// No external file loading
}

my_game/
└── game.exe

Example 2

void Main()
{
	Texture texture{ U"example/windmill.png" };
}

my_game/
├── game.exe
└── example/
    └── windmill.png

Example 3

void Main()
{
	Texture texture{ U"asset/title.png" };
	Audio audio{ U"asset/bgm.mp3" };
}

my_game/
├── game.exe
└── asset/
    ├── title.png
    └── bgm.mp3

Example 4

void Main()
{
	INI texture{ U"config.ini" };
	JSON json = JSON::Load(U"save.json");
}

my_game/
├── game.exe
├── config.ini
└── save.json

9.3 File Embedding (For Those Familiar with Siv3D)

You can embed image and audio files used in your work into the executable file. For details, see Tutorial 30 | Resource File Embedding .

9.4 Reducing Executable File Size (For Those Familiar with Siv3D)

Executable file size can be reduced by removing embedded files for unused Siv3D features. For details, see section 41.10 of Zenn Siv3D Tutorial 41 | App Publishing . Be careful during this process, as accidentally deleting necessary files can cause programs to malfunction or fonts not to display.

For web versions, there are different file size reduction methods. Check the Web Version Usage Guide or consult on the Siv3D Discord server.

9.5 Submitting Complete File Set

Please submit one ZIP file compressed with all files necessary for game execution. There are two submission methods in the work registration form:

  1. Upload the ZIP file to online storage like Google Drive or Dropbox with public settings and submit the download URL.
  2. Upload the ZIP file directly from the form.

10. Source File Submission Method

Siv3D projects contain many files. For source file submission, you can get by with submitting only minimal files. The recommended approach is to publish only Main.cpp and files you added or modified to Gist or a GitHub repository and submit that URL.

A. When Complete with One Source Code (Publish with GitHub Gist)

Directory Structure Example
ProjectDirectory/
│
└── Main.cpp

Method A Sample

If you completed your game using only Siv3D's bundled fonts, emoji, and icons with just one source file Main.cpp, the simplest approach is to publish only Main.cpp on GitHub Gist. GitHub Gist can include multiple files. Add README.md as needed to write explanations.

B. When Consisting of Multiple Source Codes (Same Directory) (Publish with GitHub Gist)

Directory Structure Example
ProjectDirectory/
│
├── Main.cpp
├── Common.hpp
├── Title.hpp
├── Title.cpp
├── Game.hpp
└── Game.cpp

Method B Sample

If you completed your game using only Siv3D's bundled fonts, emoji, and icons with multiple source files (.cpp / .hpp) in the same directory, the simplest approach is to publish those source files (.cpp / .hpp) on GitHub Gist. GitHub Gist can include multiple files. Add README.md as needed to write explanations. If there are many files, you can also choose method C.

C. When Consisting of Multiple Hierarchical Source Codes (Publish with GitHub Repository)

Directory Structure Example
ProjectDirectory/
│
├── Main.cpp
├── Common.hpp
│
├── Title/
│	├── Title.hpp
│	└── Title.cpp
│
└── Game/
	├── Game.hpp
	└── Game.cpp

Method C Sample

If you completed your game using only Siv3D's bundled fonts, emoji, and icons with multiple source files (.cpp / .hpp) in hierarchical directories, publishing source files (.cpp / .hpp) in a GitHub repository is optimal. Add README.md as needed to write explanations.

Since Siv3D users can easily create projects, you don't need to publish project files (.sln / .xcodeproj / .vcxproj).

D. When Using External Files Like Images, Audio, Text (Publish with GitHub Repository)

Directory Structure Example
ProjectDirectory/
│
├── Main.cpp
├── Common.hpp
│
├── Title/
│   ├── Title.hpp
│   └── Title.cpp
│
├── Game/
│   ├── Game.hpp
│   └── Game.cpp
│
└── App/
    ├── asset/
    │   ├── image1.png
    │   └── image2.png
    │
    └── config.ini

Method D Sample

When you place external files like images, audio, and text in the App folder, publishing source files (.cpp / .hpp) and the App folder differences (files you added) in a GitHub repository is optimal. Add README.md as needed to write explanations.

E. For More Complex Cases (Publish with GitHub Repository)

For more complex cases, please publish source files and related files in a GitHub repository to the extent possible. Use the .gitignore file for Siv3D projects as needed.

F. Direct Upload

If you don't have a GitHub account or don't understand the above methods, you can directly upload a ZIP file containing all source code.